From: Mark Alan <varia@e-healthexpert.org>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] private lists with mlmmj
Date: Wed, 08 Dec 2010 13:11:31 +0000 [thread overview]
Message-ID: <4cff8412.87f4d80a.4067.18db@mx.google.com> (raw)
In-Reply-To: <AANLkTikNkR-mQiMo2f3MVOStmn2VSgOat+O3Pbe0iAdO@mail.gmail.com>
On Wed, 8 Dec 2010 11:26:18 +0100, Florian Effenberger
<floeff@gmail.com> wrote:
> * archives are available to all subscribers with ther individual
> username and password
> * every subscriber can change his address on his own
>
> ideas on how to deal with the above to problems?
1. We already have each user ID (in the form of his/her email address)
in list_name/subscribers.d. What we need is to store their
individual passwords.
2. We could also store the password data in that file (or in another
file named with a .pwd extension), much like dovecot does:
mark@example.com:{PLAIN}hello123
mark@example.com:{SSHA}1eiCI92yj1kwLNeqsRQWgpqtdZ/HPoVR
mark@example.com:{DIGEST-MD5}5a822514317b76bde6f0e92ad76c2c76 The above
3. Data format:
{PLAIN} is plain text
The following were made using dovecotpw (which is part of the
dovecot-common package):
{SSHA} dovecotpw -p "hello123" -s SSHA
{DIGEST-MD5} dovecotpw -p "hello123" -s DIGEST-MD5 -u
mark@example.com This pwd schemes are further explained here:
<http://wiki.dovecot.org/Authentication/PasswordSchemes>
5. With such userID/password pairs, it would be rather
straightforward to let the user in:
- either from an email like:
list_name+command+mark{DIGEST-MD5}5a822514317b76bde6f0e92ad76c2c76@example.com
- or from a ordinary .php web form served from:
https://webmlmmj.example.com
Either way, no need for the inflexible and rather limited (and less
secure !) .htaccess files (which are also rather cumbersome to have if
one is not using apache as the web server)
Thank you.
M.
next prev parent reply other threads:[~2010-12-08 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 10:26 [mlmmj] private lists with mlmmj Florian Effenberger
2010-12-08 13:11 ` Mark Alan [this message]
2010-12-08 14:03 ` Ben Schmidt
2010-12-09 13:04 ` Ben Schmidt
2011-02-03 9:13 ` Florian Effenberger
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=4cff8412.87f4d80a.4067.18db@mx.google.com \
--to=varia@e-healthexpert.org \
--cc=mlmmj@mlmmj.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.