Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <l2ehtr$1a1$2@dont-email.me>
References: <l2e6cp$vs9$1@dont-email.me> <mailman.544.1380632838.18130.python-list@python.org> <l2ehtr$1a1$2@dont-email.me>
Date: Tue, 1 Oct 2013 15:27:57 +0200
Subject: Re: JUST GOT HACKED
From: =?UTF-8?B?Q2hyaXMg4oCcS3dwb2xza2HigJ0gV2Fycmljaw==?= <kwpolska@gmail.com>
To: =?UTF-8?B?zp3Or866zr/Pgg==?= <nikos.gr33k@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.552.1380634080.18130.python-list@python.org>
Lines: 69
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:55197

On Tue, Oct 1, 2013 at 3:15 PM, =CE=9D=CE=AF=CE=BA=CE=BF=CF=82 <nikos.gr33k=
@gmail.com> wrote:
> =CE=A3=CF=84=CE=B9=CF=82 1/10/2013 4:06 =CE=BC=CE=BC, =CE=BF/=CE=B7 Mark =
Lawrence =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:
>>
>> On 01/10/2013 10:58, =CE=9D=CE=AF=CE=BA=CE=BF=CF=82 wrote:
>>>
>>> Just logged in via FTP to my server and i saw an uploade file named
>>> "Warnign html"
>>>
>>> Contents were:
>>>
>>> WARNING
>>>
>>> I am incompetent. Do not hire me!
>>>
>>> Question:
>>>
>>> WHO AND MOST IMPORTNTANLY HOW DID HE MANAGED TO UPLOAD THIS FILE ON MY
>>> ACCOUNT?
>>>
>>> PLEASE ANSWER ME, I WONT GET MAD, BUT THIS IS AN IMPORTANT SECURITY RIS=
K.
>>>
>>> SOMEONES MUST HAVE ACCESS TO MY ACCOUNT, DOES THE SOURCE CODE OF MY MAI=
N
>>> PYTHON SCRIPT APPEARS SOMEPLACE AGAIN?!?!
>>
>>
>> Would you please stop posting, I've almost burst my stomach laughing at
>> this.  You definetely have a ready made career writing comedy.
>
>
> Okey smartass,
>
> Try to do it again, if you be successfull again i'll even congratulate yo=
u
> myself.
>
> --
> https://mail.python.org/mailman/listinfo/python-list

It looks like you are accusing someone of doing something without any
proof whatsoever.  Would you like help with the fallout of the lawsuit
that I hope Mark might (should!) come up with?

Speaking of =E2=80=9Ctry again=E2=80=9D, I doubt it would be hard=E2=80=A6 =
 As long as a FTP
daemon is running somewhere (and you clearly do not know better); or
even you have a SSH daemon and you do not know better, an attacker
can:

a) wait for you to publish your password yet again;
b) get you to download an exploit/keylogger/whatever;
c) brute-force.

Well, considering it=E2=80=99s unlikely you actually have a long-as-shit
password, (c) is the best option.  Unless your password is very long,
in which case is not.

I=E2=80=99m also wondering what language your password is in.  If you actua=
lly
used a Greek phrase, how long will it take you to get locked out due
to encoding bullshit?

--=20
Chris =E2=80=9CKwpolska=E2=80=9D Warrick <http://kwpolska.tk>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense