From: Stanley Lieber <email@example.com> To: firstname.lastname@example.org Subject: Re: [9front] werc got "hacked" Date: Thu, 31 Mar 2022 18:46:11 -0400 [thread overview] Message-ID: <99997C9F-FB03-43A6-9BC3-E2FF97DEB762@stanleylieber.com> (raw) In-Reply-To: <CAFSF3XNcjWp_=KD7-BoRyC7RTo8zghYOsuvR9wLz0rwmRnJUhQ@mail.gmail.com> meanwhile, all werc accounts have been disabled. sl > On Mar 31, 2022, at 6:34 PM, hiro <email@example.com> wrote: > > some 4chan has looked into the werc and found some files, some of > which seem to be the werc passwords. > > posting here in case somebody has a werc password that is also used in > other places. >
next prev parent reply other threads:[~2022-04-01 0:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 9:38 hiro 2022-03-31 22:46 ` Stanley Lieber [this message] 2022-04-02 19:43 ` Hensley 2022-04-02 20:42 ` Stanley Lieber
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=99997C9F-FB03-43A6-9BC3-E2FF97DEB762@stanleylieber.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [9front] werc got "hacked"' \ /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
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).