Am Donnerstag 14 Januar 2010 12:22:40 schrieb Alon Bar-Lev: > Yes. > I tried to... > But I cannot commit to opensc svn... > Something was changed... Andreas instructed not to use GnuTLS enabled > webdav... But I use OpenSSL... I need some time this week-end to > investigate why I cannot use https protocol in order to connect to > opensc's svn anymore.
btw, plain openssl doesn't work any more either: openssl s_client -connect opensc-project.org:443 ... GET /svn/opensc/ HTTP/1.0 results in this error on my ubuntu: depth=0 /CN=www.opensc-project.org verify error:num=18:self signed certificate verify return:1 depth=0 /CN=www.opensc-project.org verify return:1 10811:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:1053:SSL alert number 40 10811:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:990: but svn still works alias svn='LD_PRELOAD=/usr/lib/libneon.so.27 svn' svn ls https://www.opensc-project.org/svn/opensc/ branches/ releases/ tags/ trunk/ if we need to fix the server for this: we could drop all certificates and issue username/password for each developer instead. sure, hacking up svn to support smart cards and using those would be cooler, but didn't work out so far. so migrating to user/pw authentication would be the practical way to fix this. Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
