[asterisk-dev] Subversion doesn't like origsvn
thedavidfactor at gmail.com
Tue Feb 22 14:14:54 CST 2011
Is it possible that I have the wrong/old CA cert locally?
On Tue, Feb 22, 2011 at 3:11 PM, Kevin P. Fleming <kpfleming at digium.com>wrote:
> On 02/22/2011 01:36 PM, Simon Perreault wrote:
>> On 2011-02-22 13:57, David Ruggles wrote:
>>> Anyway, I'm running into a weird problem, when I try to check out I get
>>> the following error:
>>> #svn co https://origsvn.digium.com/svn/asterisk asterisk-trunk
>>> svn: OPTIONS of 'https://origsvn.digium.com/svn/asterisk': Certificate
>>> verification error: signed using insecure algorithm
>> Kevin Fleming taught me this trick. I did it so many times that I know
>> it by heart.
>> $ echo '%_topdir %(echo $HOME)/rpmbuild'>~/.rpmmacros
>> $ yumdownloader --source neon
>> $ rpm -ivh neon-...src.rpm
>> $ cd ~/rpmbuild/SPECS
>> $ vi neon.spec
>> (replace gnutls with openssl)
>> $ rpmbuild -ba neon.spec
>> $ sudo rpm -Uvh --force ../RPMS/x86_64/neon-...rpm
>> Basically, you rebuild the neon RPM to use openssl instead of gnutls.
> I though we had already created a new cert (and CA cert) for origsvn and
> put it in place... months ago.
> Kevin P. Fleming
> Digium, Inc. | Director of Software Technologies
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> skype: kpfleming | jabber: kfleming at digium.com
> Check us out at www.digium.com & www.asterisk.org
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev