Timeline for Bash evaluation using crazy passwords
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 26, 2018 at 1:01 | vote | accept | Christian Bongiorno | ||
| Sep 13, 2018 at 19:32 | |||||
| Jun 25, 2018 at 7:45 | comment | added | Toby Speight |
Portable sed command lines have exactly one command per -e argument (writing ; in place of the newline is a common, but not universal, extension to POSIX). Also, given this is Bash, $'\001' is simpler than your echo command (but I don't agree with your recommendation not to simply use distinct characters for the delimiters; I like ! or # when / is unsuitable, others choose , - instead, make the variables safe for interpolation, e.g. s!pattern!${replacement//!/\!}!)
|
|
| Jun 23, 2018 at 2:55 | comment | added | Christian Bongiorno | It didn't even occur to me that sed might choke on something but a slash is entirely within the realm of password chars that might be chosen. Thanks! I was thinking more like bash and "" doing weird things | |
| Jun 22, 2018 at 14:27 | history | answered | hjpotter92 | CC BY-SA 4.0 |