CAcert System Admins discussion list

["Martin Gummi (CAcert.org)" <martin.gummi AT cacert.org>]

Moin,

add URL Rewrite for old blog links in http and https apache config

RewriteRule ^/[0-9]{4}/[0-9]{2}/([0-9]+)\.html$ ?p=$1 [R=302,L]


-- 
mit freundlichen Grüßen / best regards
Martin Gummi
CAcert Assurer 
CAcert Arbitrator, CAcert Case Manager
CAcert.org - Free Certificates
E-Mail: 
martin.gummi AT cacert.org



On 13.07.2013 23:42, Mario Lipinski wrote:
> Apache documentation reads:
>
>>         #   Certificate Authority (CA):
>>         #   Set the CA certificate verification path where to find CA
>>         #   certificates for client authentication or alternatively one
>>         #   huge file containing all of them (file must be PEM encoded)
>>         #   Note: Inside SSLCACertificatePath you need hash symlinks
>>         #         to point to the certificate files. Use the provided
>>         #         Makefile to update the hash symlinks after changes.
> That means for me, using one file should work. Did not work, went with
> the second option. Copied mostly the old config, but here the first
> option seemed easier.
>
> Documentation on the wiki: working on it.
>
> Mario
>
> Am 13.07.2013 23:29, schrieb 
> ulrich AT cacert.org:
>> The SSL server cert root reference works with one chain file ...
>> the Client cert verification don't work this way ...
>> and is a complete separated configuration ...
>>
>> but what's about documentation in the wiki, isn't it ?!?  ?-)
>>
>> regards, uli   ;-)
>>
>> -----Original Message-----
>> From: Mario Lipinski 
>> [mailto:mario AT cacert.org]
>>  
>> Sent: Saturday, July 13, 2013 10:29 PM
>> To: 
>> ulrich AT cacert.org
>> Cc: 
>> cacert-sysadm AT lists.cacert.org
>> Subject: Re: CAcert Blog
>>
>>
>> Hi,
>>
>> the issue for logging in with a Class 3 client certificate should be
>> solved now.
>> Apparently Apache requires to supply a directory with each certificate
>> in a separate file and c_rehash applied and not a file with more than
>> one certificate if it should support multiple CAs.
>>
>> Mario
>>
>> Am 13.07.2013 21:59, schrieb 
>> ulrich AT cacert.org:
>>> me too  ...
>>> receiving   (Fehlercode: ssl_error_certificate_unknown_alert)
>>>
>>> using class3 client cert
>>>
>>> regards, uli   ;-)
>>>
>>> -----Original Message-----
>>> From: Mario Lipinski 
>>> [mailto:mario AT cacert.org]
>>>  
>>> Sent: Saturday, July 13, 2013 9:54 PM
>>> To: Martin Gummi (CAcert.org)
>>> Cc: 
>>> cacert-sysadm AT lists.cacert.org
>>> Subject: Re: CAcert Blog
>>>
>>>
>>> Hi Martin,
>>>
>>> Class 1 or Class 3?
>>>
>>> Mario
>>>
>>> Am 13.07.2013 21:51, schrieb Martin Gummi (CAcert.org):
>>>> Hello Mario,
>>>>
>>>> i can not login to the blog
>>>>
>>>> (Error code: ssl_error_certificate_unknown_alert)
>>>>
>>>>
>>>> On 13.07.2013 20:49, Mario Lipinski wrote:
>>>>> Hi,
>>>>>
>>>>> The CAcert Blog VM has been reinstalled to feature a current debian
>>>>> system. Wordpress was installed in the latest version. With this also
>> a
>>>>> new Theme had to be created to be compatible with the current version
>>> of
>>>>> the blog software.
>>>>>
>>>>> Please let me know, if anything was broken by the upgrade or anything
>>>>> does not work for you as expected.
>>>>>
>>>>>
>>>>> Mario
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature