[!] Bummer: local variable 'priv_status' referenced before assignment about smbmap HOT 7 CLOSED

It seems that you pushed the fix for this issue after releasing v1.9.1 (even though it was before you increased the version number).

This results in Kali Linux (which in turn just uses the package from Debian Testing) showing an smbmap version of v1.9.1 which still is affected by this bug.

As far as "I'm not even sure that code path should be executing": I encountered this on two recent penetration testing assignments.
While the "buggy" package worked against a Synology NAS, it failed when trying to list SMB shares on a Windows domain controller.

Would it be possible to simply push a new bugfix release that incorporates the fix, which would then be used by Debian as the source for a new package?

from smbmap.

I recently pushed some updates that should have addressed this. The "priv_status" variable was declared before use, addressed some other bugs, and tagged a new release. Did you update to the latest release? Let me know and I'll dig back in if I closed this one too early. Thanks!

from smbmap.

from smbmap.

I made sure the priv_status var was declared. Thanks again!

from smbmap.

Nice work. Thanks 👍

from smbmap.

Hi, any news about the issue recalled by @shaaati? I run into the same problem...

from smbmap.

Looks good to me. It seems you pushed 1.9.2 the same day I made my comment. Maybe that overlapped. I guess the next step is to get Debian to build a new package based on 1.9.2, but there's nothing that you need to do.

from smbmap.