Skip to content
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

failes to install on Debian 8 3.16.43-2 x86_64 #26

Closed
emptysec opened this issue Jun 2, 2017 · 7 comments
Closed

failes to install on Debian 8 3.16.43-2 x86_64 #26

emptysec opened this issue Jun 2, 2017 · 7 comments

Comments

@emptysec
Copy link

emptysec commented Jun 2, 2017

Vlany failes to install on a fresh Debian 8 3.16.43-2 x86_64 VM with a quick_install.sh.
The installations works apparently:
...

Hidden directory: /lib/libc.so.xxx.92
Environment variable: DFUTUELYMIJR
Installation finished.

but

  1. if you check the hidden directory:
    $> ls /lib/libc*
    ls: cannot access /lib/libc.so.xxx.92: No such file or directory

  2. the /boot/grub/grub.cfg wasn't patched at all.

  3. after the reboot the systems start the infinite loop:

A start job is running for udev Kernel device ... etc.

Don't know if the post reboot messages are cause of non-patched grub.cfg or are these symptoms of some other error.

BTW vlany works like a charm on Ubuntu 14.04, kudos for a great job.

@unixfox
Copy link
Collaborator

unixfox commented Jun 3, 2017

It doesn't fail, vlany is correctly installed. You should try to connect using the ssh backdoor, it have to work because I successfully installed vlany multiple times on Debian 8.
And for the infinite reboot, it's a known bug that udev fails to start because you are running on systemd. Actually the patch works only on grub legacy and not grub2.

@unixfox
Copy link
Collaborator

unixfox commented Jun 3, 2017

I'll close this issue because it's already reported here: #21

@unixfox unixfox closed this as completed Jun 3, 2017
@emptysec
Copy link
Author

emptysec commented Jun 3, 2017

Sorry for a improper formulation. Yes, i could connect to the box. I understand the grub issue now, thanks for pointing that out.
But why does the ls /lib/libc* command show the error message just after the succesfull installation ? The /lib/libc.so.xxx.92 was hidden properly on a Ubuntu 14.04 box .

@unixfox
Copy link
Collaborator

unixfox commented Jun 3, 2017

I don't really know why but the goal is done : the files of the backdoor are inaccessible.

@mempodippy
Copy link
Owner

ls /lib/libc* shows that error message after the installation because you're still in the original bash shell. New shells spawned after installation won't have this issue.

@emptysec
Copy link
Author

emptysec commented Jun 4, 2017

thanks, now it makes sense :)
BTW I've replaced ro -> rw in a GRUB2 file /etc/grub.d/10_linux and run update-grub as recommended in issues/21 but no luck, the box still bricks on reboot with a 'A start job is running' message.

@unixfox
Copy link
Collaborator

unixfox commented Jun 4, 2017

I've already tried too on the mentioned issue.
Can you continue the discussion on the original issue: #21 ? Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants