Conversation
Format.getDbms() now falls back to conf.dbms (and Backend.getDbms() falls back to conf.dbms as well) when kb.dbms isn't set yet, so a version-only result no longer drops the DBMS name or prints "None". _resumeDBMS() in target.py now also sets Backend's DBMS/version when resuming a session where the DBMS wasn't previously fingerprinted. Also simplifies several option.py helpers (non-SQL technique lookup, tamper priority validation, kb.chars/multibit setup) and adds unit tests for the getDbms() fallback behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
that is not how this is done. changing 4 files for sqlmap, without even opening an issue or asking whether you could do it will always result with close down |
|
you really think that i could merge something like |
|
Ok, I'll try to provide a working test for this, it's hard to reproduce, "sometimes" I'm hitting that bug. |
|
man, you open an issue describing your "problem", then you leave me to try to fix it. if i get stuck (i doubt it), you can do your pull request. that's the way this story goes. this is wrong repo for gaining merge points |
|
not looking for gain any points. will track correct way. thank you for explanation. |
Summary
Format.getDbms()/Backend.getDbms()now fall back toconf.dbmswhenkb.dbmsisn't set yet, so a formatted DBMS+version string no longer drops the DBMS name or prints "None" before fingerprinting completes._resumeDBMS()inlib/core/target.pynow also propagates the DBMS/version intoBackendwhen resuming a session where the DBMS wasn't previously stored, and preserves the previously detected version when the resumed value is unknown.lib/core/option.py(non-SQL technique switch validation, tamper priority check,kb.chars/kb.multibitinitialization).tests/test_misc.pycovering theFormat.getDbms()fallback behavior.Test plan
python tests/test_misc.py(newTestFormatGetDbmscases pass)