emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Burtzlaff <andy13@gmx.net>
To: Ben Finney <ben+emacs@benfinney.id.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Gmane readers - please subscribe
Date: Tue, 27 Apr 2010 17:28:53 +0200	[thread overview]
Message-ID: <20100427172853.39e82a77.andy13@gmx.net> (raw)
In-Reply-To: <87ljc9jjqt.fsf@benfinney.id.au>

On Tue, 27 Apr 2010 20:02:50 +1000
Ben Finney <ben+emacs@benfinney.id.au> wrote:

> [...]
> For an infrequently-to-never used passphrase, one of two things is the
> case: either it's unique, or it is identical to the passphrase that
> accesses some other set of services for the user.
> 
> Since it's an infrequently-to-never accessed service, it's an
> unreasonable burden to expect the user to maintain unique passphrases
> for every such service. If for this list, why not for every such list?

An idea to generate unique passwords for different services is to take
the first N characters of the hash of a string that is the
concatenation of the domain name and a master password.
I have a page on my site that does just that in javascript.
No need to maintain anything.
Frequently used passwords are stored in firefox or occasionally even in
my head.

The equivalent bash command I use for the orgmode list is:

echo -n "<masterpassword>lists.gnu.org" | md5sum | awk '{print substr ($1,0,7)}'

Andreas 

  parent reply	other threads:[~2010-04-27 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26  6:19 Gmane readers - please subscribe Carsten Dominik
2010-04-26 20:43 ` Mikael Fornius
2010-04-27  0:16 ` Ben Finney
2010-04-27  2:14   ` Tyler Smith
2010-04-27 10:02     ` Ben Finney
2010-04-27 12:04       ` Sebastian Rose
2010-04-27 13:51         ` Ben Finney
2010-04-27 18:22           ` Manish Sharma
2010-04-27 13:15       ` Tyler Smith
2010-04-27 13:16       ` Tim Landscheidt
2010-04-27 14:05       ` Nick Dokos
2010-04-27 15:28       ` Andreas Burtzlaff [this message]
2010-04-27 15:51       ` Sebastian Rose
2010-04-27 22:53         ` Ben Finney

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100427172853.39e82a77.andy13@gmx.net \
    --to=andy13@gmx.net \
    --cc=ben+emacs@benfinney.id.au \
    --cc=emacs-orgmode@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).