Domain: bofh.net
Stories and comments across the archive that link to bofh.net.
Comments · 19
-
Re:Had one of those idiots too.
... ask them to repeat all the commands on multiple occasions, tell them that the commands don't work, put them on hold (phone to the speakers playing thrash metal works really well), laugh at their stupidityIn other words, pretend you're a luser?
-
List of warez ftp sites... regularly updatedList of warez ftp sites... regularly updated.
General information on accessing these sites:
- Some sites are slow, down, whatever. Try again later.
- These sites use advanced authentication methods, such as reverse authentication look-up to local FTP daemon. Anonymous might not allways work if the address that you're coming from doesn't look 3l33+ enough, you might have to use your own userid and password. Also, disabling or enabling a proxy might help.
- Also, simple PC's with Wind0wz are also totally off the limits. Go to your shell account and use a real operating systems. L4m3rs without multitasking can't get in.
-
Re:This is linux's strength, actually
-
It's the warez network
It's not just this trojan, the whole Elite Warez Network is leeching your porn.
-
They're leeching from the warez network!
OMG! They're leeching from The Elite Warez Network! YRLY!
-
Sure they do!> However, our needs are unlikely to ever require a full time person, so I'm wondering if small, offsite sysadmin services exist
Sure they do!
Send an email to these guys, and tell them they're interested in outsourcing your system adminstration tasks. I did, and they got me set up in a jiffy.
By the way, what was your username again? >clickity-click<
-
k3wl w4r3z sitezzz!warez.bofh.org.uk
warez.satanic.org
warez.cybernothing.org
warez.dsnet.com
warez.opus1.com
aNd m4nI m03r!!!!!11!!@!@How 2 ma3k yuor 0wnzor w4r3z sYt3!!!!11!@!
(Note to mods: RTFL before modding me down)
-
Re:So hows this work now?How do you track so called "naughty network traffic" when it goes to an IP with no services or servers?
Easy by monitoring for traffic with the evil bit set which will either be originating from hell or going there
:) -
Re:Ok fuck it
-
Re:Known exploits?
The Linux 2.2 and Linux 2.4 kernels have a flaw in ptrace. This hole allows
local users to obtain full privileges. Remote exploitation of this hole is
not possible. Linux 2.5 is not believed to be vulnerable.
It isn't a remote exploit. Anyone who is foolish enough to attempt to h4X0r your b0X0rz with this vulnerability is within the normal attack range of a LART.
Please, do patch any affected machines you have as soon as possible, but don't *ahem* panic.
Soko -
IM SHOCKED! Why...BOFH it!!
I'm sorry what downtime are you talking about?
:) That must be due to static electricity generated by the friction between your HDD motor and platters, it's all your fault. I think more money and funds are needed to further research this...inconvenience...after all you would'nt want to loose all your backups :) More info on BOFHhere. -
Re:Windows tech
You, sir, are definitely BOFH material...
-
As a Security Admin all I can say is.....Duh!
People at work hate me for enforcing hard passwords. (And other assorted security measures)
Basically I am a BOFH so I don't care.
Unfortunately the common joe/jill user has no clue when it comes to computer security.
You just have to resign yourself to the fact that people are not going to like you. (i.e. Security Nazi)
A good way to help *push* them towards secure passwords is to crack your own systems passwords.
You can use John the Ripper for Unix passwords OR l0pht crack for Windows systems.
Nothing disturbs an end user more then when you email them their old password,
(You have changed it to something hideous now...) and warn them that you can read their email.
If you use Microsoft systems then use the password "Account Policies" options to increase password length/complexity values.
If you use Unix try npasswd to enforce difficult passwords.
The most important factor is to get Management buy in. Try cracking some VP's passwords during a "standard audit".
Help them come up with a creative password. (First letters of a phrase work good. Throw in some numbers/metachars..)
Once I had Management buy in it was smooth sailing. Just hold their hand for a while.
-
Ask the BofH
BOFHweb has a lot of archived a.s.r material (and a lot of macho bragging about killing lusers in various creative and entirely improbably ways - you just know these guys wouldn't even dare to complain at McD's).
Ade_
/ -
Re:What to do> The Army (or any military orginization) may not be for everybody, but I thought it'd be something completly different than what I'm doing now (I'm going to be an MP... don't think you can get much different than that from a Network Administator
:).Funny, everything I've read about network administration says you'll feel right at home. The hard part will be going back to network administration after being an MP. You'll miss the rifle.
-
Here is the next step:
-
The ultimate tech supportHere's my brief analogy of the history of humanity, in computer terms.
I know you're probably joking, but seriously, the initial passing of Jesus and the resulting New Testament, are what happened to most such spectacular public miracles. Now humans are no longer so materially dependant for everything, and have more of the hookup to God and the rest of nature, all built in. What you're talking about, is a price of such permanently increased freedom, GPL-style.
Imagine if God was an OS kernel and superuser, the earth is a big userspace and filesystem, and humans are normal processes and files therein. The regular userspace can't preempt or change the kernel. In the Old Testament, it would be like an original UNIX user trying to buy new kernel features from a very rigid closed-source vendor who says, "Not yet. Do it in user space while we're working on GNU/Linux/BSD/etc, available Real Soon Now(tm) as a freely distributable CD-ROM. Here's a magic userspace workaround in the meantime."
Jesus was a normal but priviliged file or process, like a special file in
/dev or like a kernel thread, providing userspace with an independant, personal interface straight up to all the kernel functions.Then when Jesus passed on, the kernel vendor ported his interface straight to
/proc, once again directly back within kernel space. Contents of /proc don't even occupy the space of a special node file; it's merely a direct interface. That kernel interface is now completely built in, inherently and freely available to all of us through simply our faith alone if we only freely accept it.Don't listen to the BOFH. He's a sick, disgruntled former employee who was caught embezzling. Only read BOFH for the privilege of learning what not to do!
I apologize for any error or breakdown of the integrity of this analogy. It's my first attempt with it.
:) This does not mean I advocate blasphemy or spiritual or religious zealotry toward computers, free software, or any other material thing.
=== -
The ultimate tech supportHere's my brief analogy of the history of humanity, in computer terms.
I know you're probably joking, but seriously, the initial passing of Jesus and the resulting New Testament, are what happened to most such spectacular public miracles. Now humans are no longer so materially dependant for everything, and have more of the hookup to God and the rest of nature, all built in. What you're talking about, is a price of such permanently increased freedom, GPL-style.
Imagine if God was an OS kernel and superuser, the earth is a big userspace and filesystem, and humans are normal processes and files therein. The regular userspace can't preempt or change the kernel. In the Old Testament, it would be like an original UNIX user trying to buy new kernel features from a very rigid closed-source vendor who says, "Not yet. Do it in user space while we're working on GNU/Linux/BSD/etc, available Real Soon Now(tm) as a freely distributable CD-ROM. Here's a magic userspace workaround in the meantime."
Jesus was a normal but priviliged file or process, like a special file in
/dev or like a kernel thread, providing userspace with an independant, personal interface straight up to all the kernel functions.Then when Jesus passed on, the kernel vendor ported his interface straight to
/proc, once again directly back within kernel space. Contents of /proc don't even occupy the space of a special node file; it's merely a direct interface. That kernel interface is now completely built in, inherently and freely available to all of us through simply our faith alone if we only freely accept it.Don't listen to the BOFH. He's a sick, disgruntled former employee who was caught embezzling. Only read BOFH for the privilege of learning what not to do!
I apologize for any error or breakdown of the integrity of this analogy. It's my first attempt with it.
:) This does not mean I advocate blasphemy or spiritual or religious zealotry toward computers, free software, or any other material thing.
=== -
Hardware Reset?What part of hardware reset do you not understand?
Get the LART