Re: ja jak sie włamac na xp

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

Article #171831

Back to alt.pl.comp.os.hacking Previous Next

#171831

From: incuś
Date: Sat, 03 Feb 2007 22:11

29 lines
1484 bytes

Adam Wysocki <gophi.at.chmurka.net@nospam.invalid> wrote:
> Spinacz biurowy, incuś <incus@jest.kochany.pl.wytnij.com>!
> 
>>> [gophi@avenger ~]$ format c:
>>> bash: format: command not found
>>> 
>>> Co teraz?
>> 
>> Spróbuj # rm -rf /
> 
> [gophi@avenger ~]$ # rm -rf /
> [gophi@avenger ~]$
> 
> ... co teraz?
> 

Hm.

su -c 'rm -rf /'
wpisać hasło roota na aktualnej maszynie, nacisnąć enter.

Albo
sudo rm -rf /

Działa?!

-- 
incuś
GG:5196643

Technical Details

Message-ID: <223849cd8492@incus.pl>

Path:

mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news2.icm.edu.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!nemesis.news.tpi.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail

References:

<eq1lr8$ocn$1@atlantis.news.tpi.pl> <eq2clr$92t$1@aioe.org> <eq2u37$lgu$1@atlantis.news.tpi.pl> <gophi.apcoh.1170539299@news.chmurka.net> <8e47bd10a3f8@incus.pl> <gophi.apcoh.1170539638@news.chmurka.net>

Show Full Headers

Complete Article Headers

Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news2.icm.edu.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!nemesis.news.tpi.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail
From: incuś <incus@jest.kochany.pl.wytnij.com>
Newsgroups: alt.pl.comp.os.hacking
Subject: Re: ja jak sie włamac na xp
Date: Sat, 3 Feb 2007 22:11:54 +0000 (UTC)
Organization: tp.internet - http://www.tpi.pl/
Lines: 29
Message-ID: <223849cd8492@incus.pl>
References: <eq1lr8$ocn$1@atlantis.news.tpi.pl> <eq2clr$92t$1@aioe.org> <eq2u37$lgu$1@atlantis.news.tpi.pl> <gophi.apcoh.1170539299@news.chmurka.net> <8e47bd10a3f8@incus.pl> <gophi.apcoh.1170539638@news.chmurka.net>
NNTP-Posting-Host: ccq150.neoplus.adsl.tpnet.pl
Mime-Version: 1.0
X-Trace: nemesis.news.tpi.pl 1170540714 18777 83.30.140.150 (3 Feb 2007 22:11:54 GMT)
X-Complaints-To: usenet@tpi.pl
NNTP-Posting-Date: Sat, 3 Feb 2007 22:11:54 +0000 (UTC)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reply to Parent Message