El día Saturday, August 24, 2013 a las 03:53:21PM -0400, Ethan Blanton escribió:
Tres Finocchiaro spake unto us the following wisdom:
I've never much understood Pidgins perspective on this. Even base64 is
obscure enough to keep a human from reading it over the shoulder.
Unless your
Matthias Apitz spake unto us the following wisdom:
El día Saturday, August 24, 2013 a las 03:53:21PM -0400, Ethan Blanton
escribió:
Unless your password is very, very bad, a base64 encoding of the
password should be of roughly similar complexity. Therefore, anyone
who can remember your
El día Sunday, August 25, 2013 a las 09:04:42AM -0400, Ethan Blanton escribió:
Right -- if your passwords are *really really bad* and stupid, it
matters. If that's the case, though, you need to get new passwords
ASAP. My passwords are things like Oj4=puC/8jq, which is of similar
complexity
Matthias Apitz spake unto us the following wisdom:
$ echo 'Oj4=puC/8jq' | openssl enc -base64
T2o0PXB1Qy84anEK
If your assertion is that someone will remember Oj4=puC/8jq but not
T2o0PXB1Qy84anEK, then your argument has descended into the realm of
the absurd. To effectively snatch either one
And similarly, if your argument, that all passwords must be difficult to
type and must be near impossible to read over the shoulder or else they are
REALLY BAD, which in turn makes the user STUPID seems naive and ignorant to
any basic practical, efficient, easy to remember methods of
El día Sunday, August 25, 2013 a las 12:49:45PM -0400, Ethan Blanton escribió:
Matthias Apitz spake unto us the following wisdom:
$ echo 'Oj4=puC/8jq' | openssl enc -base64
T2o0PXB1Qy84anEK
If your assertion is that someone will remember Oj4=puC/8jq but not
T2o0PXB1Qy84anEK, then your
Tres Finocchiaro spake unto us the following wisdom:
And similarly, if your argument, that all passwords must be difficult to
type and must be near impossible to read over the shoulder or else they are
REALLY BAD, which in turn makes the user STUPID seems naive and ignorant to
any basic
Matthias Apitz spake unto us the following wisdom:
I think 'Oj4=puC/8jq' is much easier to memorize due to the fact, that
it has 3 groups of 3 chars each: Oj4 puC 8jq, separated by '=' and '/',
while the token T2o0PXB1Qy84anEK is much complex to memorize, don't
you agree?
That's a random
Mensaje original
Asunto: about accounts file
Fecha: Sat, 24 Aug 2013 13:07:21 -0300
De: F. Ariel Jung faj...@msn.com
Para: support@pidgin.im
is there any way to encrypt the ~/.purple/accounts.xml files?
in it is all my accounts setting saved as plain text,
is there any way to encrypt the ~/.purple/accounts.xml files? in it is
all my accounts setting saved as plain text, including my passwords,
which is not very secure
___
Support@pidgin.im mailing list
Want to unsubscribe? Use this link:
On 08/24/2013 11:13 AM, Fernando Jung wrote:
is there any way to encrypt the ~/.purple/accounts.xml files? in it is
all my accounts setting saved as plain text, including my passwords,
which is not very secure
Please see:
https://developer.pidgin.im/wiki/PlainTextPasswords
In 3.0.0, which is
I've never much understood Pidgins perspective on this. Even base64 is
obscure enough to keep a human from reading it over the shoulder.
The Unix argument seems to be pragmatic and naive in an Active Directory
dominated industry. I for one agree with the OP, clear text is frightening
to see,
Tres Finocchiaro spake unto us the following wisdom:
I've never much understood Pidgins perspective on this. Even base64 is
obscure enough to keep a human from reading it over the shoulder.
Unless your password is very, very bad, a base64 encoding of the
password should be of roughly similar
13 matches
Mail list logo
