Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
| # Purge the following packages | |
| account-plugin-aim | |
| account-plugin-facebook | |
| account-plugin-flickr | |
| account-plugin-jabber | |
| account-plugin-salut | |
| account-plugin-twitter | |
| account-plugin-windows-live | |
| account-plugin-yahoo |
| if [ $EUID != 0 ]; then | |
| echo "It's a weird tree." | |
| else | |
| echo ' _ __' | |
| echo ' / `\ (~._ ./ )' | |
| echo ' \__/ __`-_\__/ ./' | |
| echo ' _ \ \/ \ \ |_ __' | |
| echo ' ( ) \__/ -^ \ / \' | |
| echo ' \_/ " \ | o o |.. / __' | |
| echo " \\. --' ==== / || / \\ " |
Let's say somebody temporarily got root access to your system, whether because you "temporarily" gave them sudo rights, they guessed your password, or any other way. Even if you can disable their original method of accessing root, there's an infinite number of dirty tricks they can use to easily get it back in the future.
While the obvious tricks are easy to spot, like adding an entry to /root/.ssh/authorized_keys, or creating a new user, potentially via running malware, or via a cron job. I recently came across a rather subtle one that doesn't require changing any code, but instead exploits a standard feature of Linux user permissions system called setuid to subtly allow them to execute a root shell from any user account from the system (including www-data, which you might not even know if compromised).
If the "setuid bit" (or flag, or permission mode) is set for executable, the operating system will run not as the cur
| #!/bin/sh | |
| # | |
| # a simple way to parse shell script arguments | |
| # | |
| # please edit and use to your hearts content | |
| # | |
| ENVIRONMENT="dev" |