There is no screen to be detached. - hid_backdoor

[rogandawes]

There is no screen to be detached. - hid_backdoor

[mame82]

Could you please add some infos:

• What's your target OS ?
• Has the target managed to install the keyboard drivers?
• What is the output if your run sudo python /home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py by hand ?

Additionally, please check if there's content in /home/pi/P4wnP1/john to assure you cloned recursively.

[mame82]

Thanks for your compliments.

Considering your issue (I guess you use the backdoor payload):

There's a corner case, because the server for the HID channel on P4wnP1 is started from the onKeyboardUp function. If the target doesn't manage to load the keyboard drivers fast enough (or load them at all) for some reason, this server will not be started. To have the server interface available on login, it is attached to a screen. If the screen isn't running in login, you receive this error.

So be sure your target has been done loading the keyboard driver, before login via SSH. You could logout an login again with SSH if this happens, until the server is loaded or run 'sudo screen -d -r' to try to reattach the screen again

[mame82]

Do you still have problems with this?

[chris1000]

Unfortunately yes, I've even completely reinstalled Raspbian but no luck. This message was automatically generated by Gmail.

…

On Jul 31, 2017, 5:38 PM -0400, mame82 ***@***.***>, wrote: Do you still have problems with this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Floating-Feline]

Hello @mame82 I am also a huge fan of the work your doing here and am also having the same problem as chris. The target machine on my end is a windows 10 pro box 64x, version 1703. The drivers for the keyboard did install and when you run the backdoor payload by hand it gets served up, but unfortunately the client wont connect. If theres anything else you could suggest or want me to try feel free, ill be on the pc all day. Thanks!

[mrhut10]

I have the same issue.
installed all no problem, then when plug in to any of the win10 PC's i have in my home.
and log in, it never goes into the menu screen that it is meant to go into.

doesn't seem to matter how long i wait either.

[mrhut10]

sorry resolved, turns out all my issues came from not having a good USB cable.

might be a good idea to verify everyone has a working data usb cable,
it fixed the same issue everyone had above for me.

[mame82]

@Floating-Feline
Please exit the server by issuing the exit command and provide the output of:
ls -R /home/pi/P4wnP1/duckencoder/
additionally the output of
ls /dev/hidg*

[mame82]

@mrhut10 good to hear

[mame82]

@chris1000 is your problem solved?

[mrhut10]

@mame82 awesome project btw..

[Swiftb0y]

Just to give my two cents...
This is also the case when exiting from the shell and reconnecting via ssh afterwards.
So the shell would have to be started when connecting via ssh as well as when the drivers were loaded. Otherwise I have to reboot the PI. (which also makes sense)

[mame82]

@Swiftb0y this isn't an issue, but a lack of documentation.
exit ends the backdoor server, that's the purpose of that command.
On boot the server is attached to a screen, which is then attached to a users session on login (as long as the server is running).

If you want to detach the server screen, without exiting the server, use ctrl+a followed by d (see screen docs for reference.

If you want to reattach to the screen holding the server, run screen -r.

If you do multiple ssh logins, the server screen will always be detached from the former SSH session and reattached to the new one, this is how it's meant to be played!

[Swiftb0y]

Ahhh thanks. I just thought that might help with resolving the issue.

[battletux]

I seem to be getting this behaviour when connecting to OS X Sierra. If I then plug it into a windows 7 machine I get the normal server interface.

If I have sometime today (unlikely) I'll have a play and see why this happens.

[mame82]

@battletux the backdoor payload is dedicated to Windows targets. Anyway, keyboard commands like SendKeys or SendDuckyScript should work against OSX, too. So let's see where you get with testing, maybe we could fix it.

[mame82]

@chris1000 I'm closing this. Please reopen the issue if you still are facing problems

[Amon-Amarth]

@chris1000 Same thing happened to me, but i fixed it by re-creating the symbolic link in (using ln -s): P4wnP1/hidtools/backdoor/DuckEncoder.py ->../../duckencoder/duckencoder.py
P4wnP1/hidtools/backdoor/resources -> ../../duckencoder/resources/

Also for some reason when i downloaded the whole project from the website to my computer and added the file to the Pi, duckencoder folder was empty. i had to manually download everything and SCP to the Pi.

Once all of this is done, i sudo python P4wnP1.py and was able to get the menu.

Hope this helps.

BTW mame82, maybe i should open another thread for this, but when first installing the project hostpad was NOT installed. Looking at the install.sh I've found this IF statement below :

if $WIFI; then
sudo apt-get install -y dnsmasq git python-pip python-dev screen sqlite3 inotify-tools hostapd
else
sudo apt-get install -y dnsmasq git python-pip python-dev screen sqlite3 inotify-tools
fi

not sure what happened here, but i believe that $WIFI return false during the installation script....

[mkbcaptain]

There is no screen to be detatched error here.
Device is not showing up as HD Keyboard, I can ssh headless and via wifi. Please help.

Output of 'sudo python /home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py'
Traceback (most recent call last):
File "/home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py", line 855, in
HIDin_file = open(dev_file_in_path, "rb")
IOError: [Errno 2] No such file or directory: '/dev/hidg1'
Cleaning Up...
Traceback (most recent call last):
File "/home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py", line 891, in
ll.stop() # send stop event to read and write loop of link layer
NameError: name 'll' is not defined

John folder is full of stuff

Output of 'ls -R /home/pi/P4wnP1/duckencoder/'
/home/pi/P4wnP1/duckencoder/:
duckencoder.py README.md resources

/home/pi/P4wnP1/duckencoder/resources:
be.properties de.properties gb.properties pt.properties us.properties
br.properties dk.properties hr.properties ru.properties
ca.properties es.properties it.properties si.properties
ch.properties fi.properties keyboard.properties sv.properties
cs.properties fr.properties no.properties tr.properties

Output of 'ls /dev/hidg*'
ls: cannot access /dev/hidg*: No such file or directory

[jairwen]

In my case, conncted from WIFI,
`
Linux MAME82-P4WNP1 4.9.78+ #1084 Thu Jan 25 17:40:10 GMT 2018 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Apr 11 10:34:40 2018 from 172.24.0.67
suThere is no screen to be detached.
pi@MAME82-P4WNP1:~
manual launch it.sudo python /home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py
Traceback (most recent call last):
File "/home/pi/P4wnP1/hidtools/backdoor/P4wnP1.py", line 27, in
from pydispatch import dispatcher
ImportError: No module named pydispatch`

Seems Installation is not complete. I will reinstall it again.

[mame82]

You could use the pre-build image from the release

[jackinchy]

Turns out for me also that a faulty USB cable was the issue. I would recommend swapping it out if you have any problems of the same sort.