Slashdot Mirror
Linux Virus Alert
marcjw writes: "I don't see many of these (Linux virus alerts). In fact none in the six months or so since I've switched from MS. Maybe that's why this story from newsbytes caught my eye. At any rate, I'm not sure if this poses much of a threat to the general Linux community but it's always best to be forewarned."
I don't understand this at all! Six months ago you stopped using MS and are using Linux? Probably Red Hat. You don't hear much about "viruses" or worms, but if you're running Red Hat you've probably been compromised already.
The fact that you haven't heard anything about "viruses" for Linux just scares me. You're probably a storm DDOS client host or something. Telnet to port 22, if you see SSH-1.5 1.2.26 you're probably already beat!
The List of Grievances with Slashdot.
Command (m for help): p
/dev/hda: 255 heads, 63 sectors, 4999 cylinders
Disk
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 486 3903763+ c Win95 FAT32 (LBA)
.
.
.
Not by Klerck
1
1
5
a
3
f
v
b
s
a
d
b
f
s
4
5
y
h
j
u
k
j
m
,
b
v
c
d
q
1
q
w
s
c
v
b
n
m
h
t
t
6
y
u
k
l
G
F
D
D
S
A
X
C
V
B
N
d
f
b
f
d
7
4
4
g
b
d
f
g
d
f
g
4
f
d
s
a
c
v
b
n
h
g
f
e
f
g
h
j
9
k
,
j
p
[
j
f
v
d
d
w
d
f
g
b
c
d
d
s
f
g
2
3
r
f
g
s
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
v
r
5
b
f
q
1
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
1
5
7
4
g
f
d
s
f
g
d
2
f
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
,
.
;
o
t
e
6
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
;
o
t
e
6
g
b
h
j
m
l
,
.
;
o
t
e
6
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
5
7
4
g
f
d
b
f
w
d
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
v
r
5
b
f
q
1
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
1
5
7
4
g
f
d
s
f
g
d
2
f
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
1
5
7
4
g
f
d
s
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
,
.
;
o
t
e
6
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
1
4
g
f
d
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
;
o
t
e
6
g
b
h
j
m
l
,
.
;
o
t
e
6
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
Not by Klerck
1
1
5
a
3
f
v
b
s
a
d
b
f
s
4
5
y
h
j
u
k
j
m
,
b
v
c
d
q
1
q
w
s
c
v
b
n
m
h
t
t
6
y
u
k
l
G
F
D
D
S
A
X
C
V
B
N
d
f
b
f
d
7
4
4
g
b
d
f
g
d
f
g
4
f
d
s
a
c
v
b
n
h
g
f
e
f
g
h
j
9
k
,
j
p
[
j
f
v
d
d
w
d
f
g
b
c
d
d
s
f
g
2
3
r
f
g
s
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
v
r
5
b
f
q
1
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
1
5
7
4
g
f
d
s
f
g
d
2
f
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
,
.
;
o
t
e
6
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
;
o
t
e
6
g
b
h
j
m
l
,
.
;
o
t
e
6
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
5
7
4
g
f
d
b
f
w
d
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
v
r
5
b
f
q
1
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
1
5
7
4
g
f
d
s
f
g
d
2
f
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
1
5
7
4
g
f
d
s
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
,
.
;
o
t
e
6
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
1
4
g
f
d
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
;
o
t
e
6
g
b
h
j
m
l
,
.
;
o
t
e
6
1
5
7
4
g
f
d
s
f
g
d
2
f
v
r
5
b
f
q
1
e
d
f
g
b
h
j
m
l
,
.
;
o
t
e
6
d
Wake up, all you linux nerds!
"I always compile everything myself!"
And how does that make you safe? Do you always read all the code too?
"I use tools that are secure, as OpenSSH!"
Good example: OpenSSH has had tens of holes just the last year. The same goes for a lot of all those other very-low-quality, or rather, typical-unix-programmer-quality, pieces of code. Realize it is crap! (Too.)
Some day all you linux nerds will have to wake up and understand that:
- There currently is no such thing as a safe mainstream OS.
- The main reason for windows machines and other typical desktop OSs being much more vulnerable is because their tools are much more capable (and badly designed from a security standpoint). The linux crowd is trying to build the same kind of capabilites, once they get there they probably will have similar problems.
Kill C, kill Unix
C is allmost as bad assembler to use for doing quality code. The sad thing is that many of those unix programmers out there are so bad designers and programmers that they neither have the skills to write good code, nor the insight of what the problems are.
Most unices have their authorization system designed upside down, which opens plenty of holes when used with the crappy software the unix programmers write. The typical unix/linux nerd doesn't even understand that it could be done in some other way.
I like unix, linux, windows, macos, herd, tops, blabla for what they do good, but all of them are crappy in lots of ways. Sadly, linux/unix-nerds and marketing people kills all initiatives to do something better. Their has been people trying, but they are proably worn out by now by those mentioned above.
no linux is for bitches.