Crash for untrusted ssl certificate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
subversion |
New
|
Undecided
|
Unassigned |
Bug Description
Trying to reproduce https:/
$ bzr checkout svn+https:/
Segmentation fault
Running this through gdb:
#0 0x4e44c7a6 in instancemethod_
at Objects/
#1 0x4e48405d in tupledealloc (op=<value optimized out>)
at Objects/
#2 0x4e44c343 in instancemethod_call (func=<value optimized out>,
arg=<value optimized out>, kw=<value optimized out>)
at Objects/
#3 0x4e4469f3 in PyObject_Call (func=<value optimized out>,
arg=<value optimized out>, kw=<value optimized out>)
at Objects/
#4 0x4e446bf0 in call_function_tail (callable=<value optimized out>,
args=<value optimized out>) at Objects/
#5 0x4e446e9f in PyObject_
format=<value optimized out>) at Objects/
#6 0xb7bbc282 in svn_swig_
cred=
realm=0x91d7e70 "https:/
cert_
at /var/tmp/
#7 0x410610b0 in ssl_server_
credentials
)
at subversion/
Looks like svn were trying to ask the user whether to accept the ssl certificate permanently, temporarily or not at all. So I guess to reproduce this you should run this command to clear the certificate:
grep -l hudson.dev.java.net ~/.subversion/
Related branches
Changed in bzr-svn: | |
importance: | Undecided → Medium |
Changed in bzr-svn: | |
status: | Fix Committed → Fix Released |
Versions involved:
* svn-bzr merge containing r1229 from svn-1.5 branch and r1218 from bug128496 branch
* subversion 1.5.0 RC9
* python 2.5.2
* swig 1.3.35