Researchers disclose a 55-year-old vulnerability affecting macOS, Windows and Linux. Exploitation is trivial and requires no special tools. No patch exists.
BTW use caution with your glob there, that only does what you described if the folder has contents, if it doesn’t, rather than getting nothing you’ll get back the parent directory, at least in bash. I’m not one of the cool zsh kids.
I may be the stupid one, i’m sure there’s a related gotcha here under some condition, but objectively not the one i described. Sorry, did not intend to waste anyone’s time and i do appreciate the response back to set me straight.
This flag is fortunately not needed as /* ensures root recipes are preserved. It’s just that anything below isn’t.
Oh i was kind of going for the opposite. 😈
BTW use caution with your glob there, that only does what you described if the folder has contents, if it doesn’t, rather than getting nothing you’ll get back the parent directory, at least in bash. I’m not one of the cool zsh kids.
Huh, are you sure or am I just stupid?
[user@device Documents]$ mkdir test [user@device Documents]$ cd test [user@device test]$ ls ./* ls: cannot access './*': No such file or directorySame behavior with * instead of ./*.
I may be the stupid one, i’m sure there’s a related gotcha here under some condition, but objectively not the one i described. Sorry, did not intend to waste anyone’s time and i do appreciate the response back to set me straight.