View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002160 | Kali Linux | Kali Package Bug | public | 2015-03-11 10:02 | 2022-01-12 10:47 |
Reporter | dookie | Assigned To | sbrun | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | kali-dev | ||||
Fixed in Version | kali-dev | ||||
Summary | 0002160: SQLmap Errors out on kali-rolling | ||||
Description | Running sqlmap against a target URL causes the following failure: root@kali:~# sqlmap -u "http://192.168.11.251/wp/" --dbs | ||||
The underlying problem is that libssl no longer supports SSLv2 and SSLv3. In turn the Python "ssl" module built against that library no longer exports those ssl.PROTOCOL_SSLv3 ssl.PROTOCOL_SSLv23 constants. So sqlmap should learn to deal with those missing constants. And for Kali we might want to reenable SSLv2/SSLv3 in libssl and rebuild python. |
|
Filed https://github.com/sqlmapproject/sqlmap/issues/1193 in the upstream project. |
|
Looks like this is already fixed in the sqlmap git repository. Let's try to update sqlmap only for now. |
|
sqlmap is updated in kali-proposed-updates and kali-dev. The new version is 1.0+git20150214-0kali1. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2015-03-11 10:02 | dookie | New Issue | |
2015-03-13 06:27 | rhertzog | Note Added: 0003161 | |
2015-03-13 06:27 | rhertzog | Assigned To | => sbrun |
2015-03-13 06:27 | rhertzog | Status | new => confirmed |
2015-03-13 06:33 | rhertzog | Note Added: 0003162 | |
2015-03-13 09:26 | rhertzog | Note Added: 0003163 | |
2015-03-16 05:36 | sbrun | Note Added: 0003167 | |
2015-03-16 05:36 | sbrun | Status | confirmed => resolved |
2015-03-16 05:36 | sbrun | Resolution | open => fixed |
2015-03-16 05:36 | sbrun | Fixed in Version | => kali-dev |
2015-11-09 13:44 |
|
Issue cloned: 0002807 |