Follow

Happy 30th Birthday /bin/bash! Thanks to its developers Brian Fox and Chet Ramey and all those who have contributed to it.

T="Happy 30th\nBirthday\n/bin/bash \!";a="-annotate +0+0";convert -size 420x300 -gravity center radial-gradient:\-purple -font Brush-Script-MT-Italic -pointsize 72 -fill yellow -stroke pink -strokewidth 15 $a "$T" -stroke yellow -strokewidth 10 $a "$T" -stroke orange -strokewidth 5 $a "$T" -stroke none $a "$T" -gravity southeast -font Helvetica -pointsize 10 -fill white -annotate +0+0 "Made in Bash with ImageMagick on a Mac" bashbirthday.png

@tdemin @climagic What system are you using? Using '/usr/bin/env/ bash' only helps to make scripts portable. However, most UNIX-based systems have /bin/bash and using env could potentially pose a security risk.

Example:
If $PATH is "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" and there is malware named "bash" in /usr/local/sbin directory (/usr/local/sbin/bash is executed instead of /usr/bin/bash because /usr/local/sbin is before /usr/bin in $PATH), then this is a security risk

@TheOuterLinux @climagic using env is not a security risk. Having /usr/local or ~/.local in your PATH before the system dirs is, and is not connected with env.

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!