On 12/07/13 10:40, Andres Perera wrote:
On Sat, Dec 7, 2013 at 4:10 AM, Jan Stary <[email protected]> wrote:
On Dec 06 02:20:49, [email protected] wrote:
conclusion: shell is not good for this
Yeah right.
Who would even think of doing this in shell.
apparently at least one person did
I was being sarcastic of course, dipshit.
you aren't in sync with the quantity of real world shells that use
temp files for heredoc, and who feature combinations of { printf
(not)? being a builtin, alternatives like ``print'' and ``echo'' are
unportable }
Indeed, I am not in sync with the quantity of real world shells
(as opposed to sh?), thank god. Christian's code is pure sh though.
what does this even mean?
some implementations of sh use tmpfiles and some don't. this isn't
about syntax differences.
Christian didn't use heredocs. What are you referring to?
You've made your points but now you're just annoying, it's not fun anymore.
/Alexander
you aren't understanding the subject, but choose to participate anyways. why?
who do you think you're impressing?
even if it keeps heredocs in memory you have no idea if it zeros it
out afterwards
Also, the letters of the password get read
by the console driver as you type them.
God knows what happens there.
On Dec 06 08:15:19, [email protected] wrote:
you use cat, muffin face:
...
STTY=`stty -g`
echo -n "Password: "
stty -echo
cat > PASSWORD_FILE_DONT_READ_IF_YOU_ARE_OTHER_PROCESS_PLS
So after typing "password" and hitting [enter],
you are still running that cat.
Just what the user expects.
