-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BKscan fixed "x11: failed to open display" issue #1
Conversation
Hi nikallass, Thanks for your PR, much appreciated.
Also what users have you specified in "Select Users"? Thanks again for improving BKScan. |
If you need, I also can provide an access to my machine on 3389 port for you to check. PM of course. :) |
I have fixed 2) in 55bbb55. Thanks. One thing to note about adding
Before adding
The only drawback of
|
Yeah, thats true. Not very good to scan twice. But it is the only way, as I see. |
Hey, in your last commit in bkscan.sh you missed: |
Just to clarify, the fix you proposed for the DISPLAY/X11 issue didn't work on my environment. Also you confirmed me by DM that it didn't completely worked after your computer went out of hibernation. So am not going to merge the changes until we confirm it actually works. |
This fixed the issue for me. Thanks, @nikallass! |
Thanks for confirming chrsjhnsn. I've merged the changes due to multiple people confirming it helped them, even if it does not work with my distrib. Closing this. Please open another issue if you still have the problem, and detail your environment. |
Check latest commit. |
1) Issue with x11:
Fixed with information from here
Working good now:
If you are using ssh to kali where is BKscan so you need to redefine $DISPLAY variable:
export DISPLAY=:1
2) Issue with xfreerdp asking username/password on hosts without NLA
Also added
xfreerdp -sec-nla /u:""
flag so scan now works on hosts without NLA, it is not asking username\password any more.If username\pass not provided, but NLA is enabled on host:
In
--debug
mode it is clear: