Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.etla.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <l2cu2k$fht$2@dont-email.me>
References: <l28m26$aao$1@dont-email.me> <l28npr$hai$1@dont-email.me> <mailman.441.1380443023.18130.python-list@python.org> <l28of9$jla$1@dont-email.me> <l28oro$jla$2@dont-email.me> <5247f6bb$0$29988$c3e8da3$5496439d@news.astraweb.com> <l28v5k$fu7$1@dont-email.me> <mailman.446.1380453107.18130.python-list@python.org> <l292n0$1cg$1@dont-email.me> <mailman.452.1380464398.18130.python-list@python.org> <l29j65$p7h$1@dont-email.me> <mailman.454.1380471288.18130.python-list@python.org> <l29jub$uc4$1@dont-email.me> <mailman.488.1380552370.18130.python-list@python.org> <l2cedj$c9d$1@dont-email.me> <mailman.498.1380566574.18130.python-list@python.org> <l2cm0d$9j$1@dont-email.me> <mailman.507.1380573909.18130.python-list@python.org> <l2cqog$scr$1@dont-email.me> <mailman.511.1380577448.18130.python-list@python.org> <l2csp7$79h$1@dont-email.me> <mailman.515.1380579301.18130.python-list@python.org> <l2cte9$fht$1@dont-email.me> <mailman.517.1380580134.18130.python-list@python.org> <l2cu2k$fht$2@dont-email.me>
Date: Tue, 1 Oct 2013 08:43:08 +1000
Subject: Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb6 in position 0: invalid start byte
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.521.1380580997.18130.python-list@python.org>
Lines: 43
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:55137

On Tue, Oct 1, 2013 at 8:30 AM, =CD=DF=EA=EF=F2 <nikos.gr33k@gmail.com> wro=
te:
> =D3=F4=E9=F2 1/10/2013 1:28 =F0=EC, =EF/=E7 Mark Lawrence =DD=E3=F1=E1=F8=
=E5:
>>
>> On 30/09/2013 23:19, =CD=DF=EA=EF=F2 wrote:
>>>
>>>
>>> 2 dickheads names Joe & Mark work together to achieve total bullshit!
>>> Well done Beavis & Butthead!
>>> rofl...
>>>
>>
>> Well aside from the fact that you've maintained your record by being
>> inaccurate with 50% of the names that you've quoted, it appears that
>> we've something that has very much in common with your website.  Which
>> reminds me, is it still possible to access your users' names and
>> passwords in plain text or is that something that you've actually
>> bothered to fix?
>
>
> Nope, it isn't. I have fixed it.

And this doesn't bother you???!?

Nikos, industry best practice is to make sure people can't steal all
your users' passwords *even if they get access to your hard drive*.
Passwords should be stored like this:

"92e25cf5beefd4982cedd2f28b430e0e9d23e0966ee3f20c74f825ebeeee9842"

That's the password "qwer", on an account named "asdf", on a mythical
system. Even knowing that, you can't work out what another password
means. Storing people's passwords in plain text is a HORRIBLE HORRIBLE
idea - and having them accessible to the world is a sign of a complete
and utter lack of any semblance of security.

I understand that bugs happen. But bugs of this criticality should be
your very highest priority... unless you're not actually in business
here, and you're just scamming a bunch of people by pretending you run
a legit enterprise.

ChrisA