🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.pl.comp.os.hacking
Article #171798

Re: Ile zajeloby zlamanie hasla?

#171798
From: z0nk
Date: Thu, 01 Feb 2007 19:09
21 lines
1620 bytes
lrem@lrem.maxnet napisał(a):
> W poście <ept85h$qqj$1@nemesis.news.tpi.pl>,
>  MB nabazgrał:
>> Witam
>>
>> Pytanka dotyczace zlamanie hasla 254 znakowego, skladajacego sie z duzych, 
>> malych liter oraz znakow specjalnych. Kodowanie 128-bit RC4.
>>
>> Ile zajeloby to na komputerach 4 rdzeniowych (zakladamy ze program umie 
>> obsluzyc 4 rdzenie)?
>>
>> Ile na dzisiejszym przecietnym komputerze?
> 5395141535403007094485264 lata.
czyli wieczność

-- 
|-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-|
| Adam Hnat  http://z0nk.ejai.jp/                             |
| jid: z0nk@bash.org.pl                                       |
| GSM: 888 411 539                                            |
|-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-|
Technical Details
Message-ID: <apcoh.1170356952@news.chmurka.net>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news2.icm.edu.pl!news.chmurka.net!not-for-mail
References: <ept85h$qqj$1@nemesis.news.tpi.pl> <slrnes4avt.8bd.lrem@lrem.maxnet>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news2.icm.edu.pl!news.chmurka.net!not-for-mail
From: z0nk <linux0_potnij_to@op.pl>
Newsgroups: alt.pl.comp.os.hacking
Subject: Re: Ile zajeloby zlamanie hasla?
Date: Thu, 01 Feb 2007 20:09:14 +0100
Organization: news.chmurka.net
Lines: 21
Message-ID: <apcoh.1170356952@news.chmurka.net>
References: <ept85h$qqj$1@nemesis.news.tpi.pl> <slrnes4avt.8bd.lrem@lrem.maxnet>
NNTP-Posting-Host: ipb229.t16.ds.pwr.wroc.pl
Mime-Version: 1.0
X-Trace: news.chmurka.net 1170356951 31528 156.17.233.229 (1 Feb 2007 19:09:11 GMT)
X-Complaints-To: usenet#chmurka.net
NNTP-Posting-Date: Thu, 1 Feb 2007 19:09:11 +0000 (UTC)
In-Reply-To: <slrnes4avt.8bd.lrem@lrem.maxnet>
User-Agent: IceDove 1.5.0.9 (X11/20061220)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit