Timeline for Make shell script contents difficult to read
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2019 at 1:25 | comment | added | Gordon Davisson |
@Wowfunhappy If you encrypt all of the final output (with openssl enc), you should be able to avoid that problem. Note that it's entirely possible to encrypt multiple strings (bits of output, prompts, etc) with the same password(s). If it's the actual program logic that needs to be hidden, that's more complicated.
|
|
| Jan 10, 2019 at 1:19 | comment | added | Wowfunhappy | Thanks! The shasum bit is great, although I think I'll need to use that compiler... even if the password answers aren't visible, the output at the end of the script is. | |
| Jan 10, 2019 at 1:16 | vote | accept | Wowfunhappy | ||
| Jan 10, 2019 at 22:32 | |||||
| Jan 10, 2019 at 1:15 | vote | accept | Wowfunhappy | ||
| Jan 10, 2019 at 1:16 | |||||
| Jan 9, 2019 at 22:43 | history | answered | Gordon Davisson | CC BY-SA 4.0 |