From: William Cheswick <ches@cheswick.com>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: NSFW passwords
Date: Tue, 12 Mar 2024 12:47:12 -0400 [thread overview]
Message-ID: <06861AF4-AB7E-451A-9C0B-AB1A24C3B23D@cheswick.com> (raw)
In-Reply-To: <CABH=_VSR8ETtzuGssj12jBOvHoBtnXMDmoWWtUiH33NKMLQUcw@mail.gmail.com>
Ron Harden’s insult generator solved the NSFW passphrase problem. It is available at
https://cheswick <https://cheswick/>.com/insults
> On Mar 12, 2024, at 12:23 PM, Paul Winalski <paul.winalski@gmail.com> wrote:
>
> One problem with random password generation is to avoid generating
> passwords that are or contain naughty words. VAX/VMS version 4.0
> added an option for random password generation. They had a very
> extensive list of naughty words in many different languages to filter
> the random passwords. During beta test they got a bug report from a
> high school. The naughty words text file was world-readable and
> students were amusing themselves by reading it. At release the file
> was protected so that only privileged users could read it.
next prev parent reply other threads:[~2024-03-12 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 14:37 [TUHS] early unix rand Douglas McIlroy
2024-03-12 16:23 ` [TUHS] " Paul Winalski
2024-03-12 16:47 ` William Cheswick [this message]
2024-03-13 1:22 ` Russ Cox
2024-03-12 16:32 ` Ken Thompson
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=06861AF4-AB7E-451A-9C0B-AB1A24C3B23D@cheswick.com \
--to=ches@cheswick.com \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).