From: Steffen "Daode" Nurpmeso <sdaoden@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] off topic: full unicode support isn't easy
Date: Wed, 24 Jul 2013 17:07:21 +0200 [thread overview]
Message-ID: <20130724160721.8B9fU6RlEJFtGetcEwilCZfl@dietcurd.local> (raw)
In-Reply-To: <20130724141211.GA73204@intma.in>
Kurt H Maier <khm-9@intma.in> wrote:
|On Wed, Jul 24, 2013 at 05:59:32AM +0300, Aharon Robbins wrote:
|> FYI
|>
|> Creative usernames and Spotify account hijacking
|> http://labs.spotify.com/2013/06/18/creative-usernames/
|>
|> Arnold
|
|Seems the thrust of this article is more like "writing secure
|public-facing authentication mechanisms relying on unvetted clownsourced
|code isn't easy".
I thought more in the direction you-are-fucked-up-if-you-trust-
anyone-but-yourself-if-not-today-then-tomorrow.
(It's Python...)
|khm
--steffen
prev parent reply other threads:[~2013-07-24 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 2:59 Aharon Robbins
2013-07-24 5:09 ` erik quanstrom
2013-07-24 21:38 ` Steffen Daode Nurpmeso
2013-07-24 23:55 ` erik quanstrom
2013-07-24 14:12 ` Kurt H Maier
2013-07-24 15:07 ` Steffen Daode Nurpmeso [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130724160721.8B9fU6RlEJFtGetcEwilCZfl@dietcurd.local \
--to=sdaoden@gmail.com \
--cc=9fans@9fans.net \
/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).