From: daniel@wagner-home.com (Daniel Wagner)
Subject: [sup-talk] 0.5 thoughts
Date: Fri, 25 Jan 2008 21:12:28 -0800 [thread overview]
Message-ID: <1201324251-sup-2682@buckwheat> (raw)
In-Reply-To: <1201323295-sup-3282@buckwheat>
Excerpts from Daniel Wagner's message of Fri Jan 25 21:03:33 -0800 2008:
> > - at least a cursory effort to not store login credentials in
> > plaintext .. how to store them whilst retaining simplicity and
> > platform independence is an interesting question. Not sure how far sup
> > (or anyone really) wants to go down that particular rabbit hole
>
> I don't like this idea. I think it was Gaim (now Pidgin) that first
> opened my eyes to the possibility that plaintext passwords might not be
> so bad. The Pidgin page seems to be down just now, so I can't say for
> certain that this is the essay I originally read, but
> http://developer.pidgin.im/wiki/PlainTextPasswords?format=txt
> sounds like a promising result from Google.
Wait, now that I stopped to think about it, I may have to take this
back. I don't actually know what credentials you mean, so the argument
may not even apply.
~d
next prev parent reply other threads:[~2008-01-26 5:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 5:59 William Morgan
2008-01-25 6:22 ` John Bent
2008-01-25 16:52 ` William Morgan
2008-01-25 20:37 ` Nicolas Pouillard
2008-01-25 22:31 ` John Bent
2008-01-25 11:12 ` Sho Fukamachi
2008-01-25 11:26 ` Nicolas Pouillard
2008-01-31 13:24 ` Giorgio Lando
2008-02-08 1:09 ` William Morgan
2008-02-08 8:42 ` Giorgio Lando
2008-01-26 5:03 ` Daniel Wagner
2008-01-26 5:12 ` Daniel Wagner [this message]
2008-01-25 13:22 ` vasudeva
2008-01-26 0:37 ` John Bent
2008-01-26 1:00 ` vasudeva
2008-01-25 14:46 ` John Bent
2008-01-26 3:56 ` Christopher Warrington
2008-01-26 5:05 ` Daniel Wagner
2008-01-27 16:16 ` Giorgio Lando
2008-01-27 20:29 ` Marcus Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201324251-sup-2682@buckwheat \
--to=daniel@wagner-home.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox