Timeline for Ask for a password in POSIX-compliant shell?
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 8, 2022 at 8:03 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
deleted 6 characters in body
|
| May 8, 2022 at 7:52 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 337 characters in body
|
| Apr 9, 2022 at 20:58 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 199 characters in body
|
| S Apr 9, 2022 at 20:49 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 179 characters in body
|
| Apr 9, 2022 at 17:38 | review | Suggested edits | |||
| S Apr 9, 2022 at 20:49 | |||||
| Jul 12, 2019 at 14:25 | vote | accept | Hey | ||
| Aug 19, 2015 at 19:38 | comment | added | Barmar |
Thanks for showing how to save and restore the old stty settings.
|
|
| Aug 14, 2015 at 10:25 | comment | added | Stéphane Chazelas |
@hildred, note that the quotes in REPLY="$(...)" don't harm (except for the SE syntax highlighting) but are not necessary
|
|
| Aug 14, 2015 at 5:36 | comment | added | Stéphane Chazelas | @JohnKugelman here docs are written as temporary files in most shells while printf is built in most shells. I'm not sure which is best. | |
| S Aug 14, 2015 at 0:18 | history | edited | hildred | CC BY-SA 3.0 |
added double quotes to handle passwords which contain whitespace.
|
| S Aug 14, 2015 at 0:18 | history | suggested | Parthian Shot | CC BY-SA 3.0 |
added double quotes to handle passwords which contain whitespace.
|
| Aug 13, 2015 at 22:35 | review | Suggested edits | |||
| S Aug 14, 2015 at 0:18 | |||||
| Aug 13, 2015 at 21:13 | comment | added | John Kugelman |
Might cat + heredoc be a safer alternative to the printf?
|
|
| Aug 13, 2015 at 13:10 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 |
added 704 characters in body
|
| Aug 13, 2015 at 13:04 | history | answered | Stéphane Chazelas | CC BY-SA 3.0 |