On Dec 06 02:20:49, andre...@zoho.com 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 shel
On Sat, Dec 7, 2013 at 4:10 AM, Jan Stary wrote:
> On Dec 06 02:20:49, andre...@zoho.com 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
On Thu, Dec 05, 2013 at 08:20:07AM +0100, obsd, cgi wrote:
> So I know the rule.. only remember a few very very long passwords (ex.:
> based on several words and a few special chars), and keep the rest of the
> passwords in a password manager (those aren't remembered and extreme long).
>
> But this
On 12/07/13 10:40, Andres Perera wrote:
On Sat, Dec 7, 2013 at 4:10 AM, Jan Stary wrote:
On Dec 06 02:20:49, andre...@zoho.com 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 o
On Dec 02 13:50:49, mhe...@gmail.com wrote:
> And there are specific needs in terms of kernel services to be able to
> route audio to/from the "phone" part of your device
Can you please elaborate on this?
When searching for a good phone-recording application,
I found that in most of them the voic
Christian Weisgerber wrote:
> --->
> #!/bin/sh
>
> SAFE=$HOME/.pwsafe
> TMPFILE=`mktemp /tmp/pwsafeXX` || exit 1
>
> trap 'rm -P "$TMPFILE"' 0 1 2 15
>
> STTY=`stty -g`
> echo -n "Password: "
> stty -echo
> read PASSWORD
> stty "$STTY"
>
> set -e
> echo -n "$PASSWORD" | op
Thus said Christian Weisgerber on Sat, 07 Dec 2013 18:52:25 +:
> Also, your editor may scatter additional cleartext copies around, for
> instance vi's recovery files.
Assuming /home is on an encrypted disk, that can be partially remedied
by using something like the following in ~/.exrc:
s
On Sat, Dec 7, 2013 at 2:22 PM, Christian Weisgerber wrote:
> Christian Weisgerber wrote:
>
>> --->
>> #!/bin/sh
>>
>> SAFE=$HOME/.pwsafe
>> TMPFILE=`mktemp /tmp/pwsafeXX` || exit 1
>>
>> trap 'rm -P "$TMPFILE"' 0 1 2 15
>>
>> STTY=`stty -g`
>> echo -n "Password: "
>> stty -ec
Hi,
Every time I boot OpenBSD (5.4-current AMD64) I get the following
message/error after a while:
acpi0: PM1 stuck (en 0x121 st 0x1), clearing
Any suggestions what the problem could be? The system runs openbox, chrome,
vim, terminator and ghc and feels much slower than when running Xubuntu
12.
9 matches
Mail list logo