We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running linpeas.sh on an Oracle Linux 7 system gets stuck at "Users with Console"
linpeas
bash ./linpeas.sh
[...] ╔══════════╣ Superusers root:x:0:0:root:/root:/bin/bash ╔══════════╣ Users with console
The script was executed both as a regular user and as root as such:
Both in a terminal multiplexer (tmux/byobu) and without.
None.
$ cat /etc/oracle-release Oracle Linux Server release 7.9
$ uname -a Linux foo 3.10.0-1160.92.1.0.1.el7.x86_64 #1 SMP Tue Jun 6 09:59:29 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux
The check that is stuck is "Users with console". No output is presented after the header.
It should progress to the next stage or fail with an error.
N/A
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue description
Running linpeas.sh on an Oracle Linux 7 system gets stuck at "Users with Console"
Steps to reproduce the issue
linpeas
into /tmpbash ./linpeas.sh
Which parameters did you use for executing the script and how did you execute it?
The script was executed both as a regular user and as root as such:
Both in a terminal multiplexer (tmux/byobu) and without.
Is there any AV / Threat protection in the system?
None.
Please, indicate the OS, the OS version, and the kernel version (build number in case of Windows)
Please, indicate the check that is failing and add a screenshot showing the problem
The check that is stuck is "Users with console". No output is presented after the header.
How did you expect it to work?
It should progress to the next stage or fail with an error.
Additional details / screenshot
N/A
The text was updated successfully, but these errors were encountered: