lexfiend

3 ms·

1. 1.▲
   by lexfiend 5y ago

   Possibly because: > The machine I am using is MacBook Pro, 2019 (2.4 GHz Quad Core i5, 8GB, 256GB SSD, Big Sur 11.1) Given the target schema, 100M rows with only 8GB RAM risks hitting swap hard.
2. 2.▲
   by lexfiend 6y ago

   25 years ago, junior sysadmin me had to restore our server's drives from tape. To my horror, all the backup tapes were corrupted. It took a while to figure out what happened; my 2am cron job script basically did this: run_backup &a
3. 3.▲
   by lexfiend 6y ago

   The simplest mitigation probably bears mentioning: Prepend all wildcarded relative paths with `./`, because `rm ./*` does what you'd expect.
4. 4.▲
   by lexfiend 6y ago

   > This "vulnerability" doesn't even need to involve a shell at all - any exec*() with the same arguments will have the same result. Wildcard expansions are done by shells, so no, exec() wouldn't trigger this "vul