From: Avalon Williams <firstname.lastname@example.org> To: email@example.com Subject: Re: [9front] 4chan hacked rc-httpd Date: Thu, 31 Mar 2022 23:54:22 +0000 [thread overview] Message-ID: <ttG_69SucNyNUvtb74BYfFu9f-uw1tTcIcIztINdKUHjLAPNjUh6DVyiOo1cceJjvnNTbDqt_9xCxcPNKG2tsOvdKRpagK5BYQZUI99wT7kfirstname.lastname@example.org> (raw) In-Reply-To: <EC93BCF8DB4A22F2A1E6CF0D3FB0C16A@5ess.inri.net> Another note to have with this is just to have better data security, in a modified version of werc I'm using I added a number of security features (though they were all designed to run on plan9port rather than on 9front itself and I never bothered porting them or contributing them because they relied on some Linux-specific commands), including a salted password hash storage system (I used sha-256 but was planning on moving it to use argos2 via a go utility). Leaks are always going to happen, its better to make the data harder to access after the fact as well as trying to prevent them in the first place. avnt ------- Original Message ------- On Thursday, March 31st, 2022 at 2:10 PM, <email@example.com> wrote: > https://boards.4channel.org/g/thread/86286230/plan-99front-is-super-secure > > mailing list subscriber lists were leaked. i don't think any other > > sensitive data was. > > if you have an auth password on one of our servers, change it now, > > just for good measure. > > sl
next prev parent reply other threads:[~2022-04-01 0:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-31 18:10 sl 2022-03-31 19:35 ` sirjofri 2022-03-31 20:17 ` Kurt H Maier 2022-03-31 20:26 ` Stanley Lieber 2022-04-03 3:26 ` sl 2022-04-03 18:05 ` adr 2022-03-31 20:29 ` ori 2022-03-31 23:54 ` Avalon Williams [this message] 2022-04-01 0:38 ` Kurt H Maier
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='ttG_69SucNyNUvtb74BYfFu9f-uw1tTcIcIztINdKUHjLAPNjUh6DVyiOo1cceJjvnNTbDqt_9xCxcPNKG2tsOvdKRpagK5BYQZUI99wT7kfirstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [9front] 4chan hacked rc-httpd' \ /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).