Security implications of forgetting to quote a variable in bash
![Security implications of forgetting to quote a variable in bash](/content/images/size/w2000/2021/01/meritt-thomas-0nDC2QgBojY-unsplash.jpg)
Security implications of forgetting to quote a variable in bash/POSIX shells
If you’ve been following unix.stackexchange.com for a while, youshould hopefully know by now that leaving a variableunquoted in list context (as in echo $var) in Bourne/POSIXshells (zsh being the
![](https://cdn.sstatic.net/Sites/unix/img/apple-touch-icon@2.png?v=32fb07f7ce26)
What is the difference between “du -sh *” and “du -sh ./*”?
What’s the difference between du -sh * and du -sh ./* ? Note: What interests me is the * and ./* parts.
![](https://cdn.sstatic.net/Sites/unix/img/apple-touch-icon@2.png?v=32fb07f7ce26)
![Buy Me A Coffee](https://cdn.buymeacoffee.com/buttons/v2/default-red.png)