From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: APOP-only POP3 clients?
Date: Fri, 27 May 2022 08:28:46 -0400 [thread overview]
Message-ID: <20220527122846.ko7nenbhnwrgixqt@meerkat.local> (raw)
In-Reply-To: <20220527105302.M842323@dcvr>
On Fri, May 27, 2022 at 10:53:02AM +0000, Eric Wong wrote:
> Which may be an extremely long username... Now I'm thinking
> it's safe for UUID_1 and UUID_2 to be the same, to save storage
> space on the server and to save users from dealing with
> excessively long, compression-unfriendly field entries. So,
> this:
> username: $UUID@$NEWSGROUP.$SLICE
> password: $UUID
1. I'd even say that we don't need all the entropy of uuid here and it's
probably sufficient to grab 8-12 bytes from /dev/random and z-base-32
encode them (z-base-32 to produce case-insensitive strings)
2. You can make password be "p" :)
-K
prev parent reply other threads:[~2022-05-27 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:53 APOP-only POP3 clients? Eric Wong
2022-05-27 12:28 ` Konstantin Ryabitsev [this message]
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220527122846.ko7nenbhnwrgixqt@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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 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).