G
Gerhard Beulke
Nah...Let's go back to PC DOS version 1.0.
Or just get a firewall, or drop in at a 'shields up' type website and
discover whether they actually have any obvious loopholes. Maybe we can
get 'running an unprotected computer on a public network' added to the
list of felonies??
GSV Three Minds in a Can said:Or just get a firewall, or drop in at a 'shields up' type website and
discover whether they actually have any obvious loopholes. Maybe we can
get 'running an unprotected computer on a public network' added to the
list of felonies??
Home users are the last in the blame game chain IMO. First comes the
a**holes that write and spread malicious code. Second is M$ for
continually releasing products unnecessarily unsafe for naive users to
use right out of the box.
It's often argued that M$ is merely giving users what they want ...
that users have a insatiable lust for all kinds of features. But I
believe M$ has actually created this lust ... with far too little
attention to security. IE and OE are bad enough disasters, but what
what really blows my mind is M$'s version of local networking. I
wouldn't touch it with a ten foot pole.
Oh BS. First off the next time you run across some perfect code post it
here.
Second, you sound like one of those people who put labels on baby walkers
warning parents not to use the walker near stairs. Well duhhhhh.
Somewhere along the line the consumer has to take on some responsibility.
In this case MS release a fix over a month ago. At that point it's up to
the user to do there part of the deal and use common since and update their
systems. (or in this case at least have a firewall).
What's really lacking is education. The average user has no idea that they
are exposed nor what that means nor what the impact can have on them and
others.
In addition, they don't know how to update their systems or why
it's important. And that's even after they are hit. Instead, in this some
one else is responsible world, they just blame MS and continue to NOT update
there systems or add some sort of firewall or find out what other measures
they can use to protect themselves.
I think we need a bunch of Safe Computing PSAs to complement the Safe Sex
PSA. Instead of It's stupid to not use a condom the can say it's stupid not
to use a firewall, AV and update your system. ;-)
Gabriele said:
First _patch_ the hole *in* FreeBSD. I found that in a PC mag
just today:
Valid for *all* versions of BSD.
That aspect of the problem I've been concerned with for a number of
years. You've got head up your arse if you believe the situation with
"stupid users" is ever going to change. Millions of gnubies go on line
yearly. Frankly, I'm fed up with the pseudo experts who have learned a
few things and inflate their little egos by going around pointing
fingers at "stupid users".
And it's not going to change, so face facts.
Naive users don't tend to blame M$. It's the "know a little bit" types
that revel in doing that.
Lotsa luck Go ahead and beat your head against the wall.
Gerhard said:Nah...Let's go back to PC DOS version 1.0.
GSV said:Bitstring
<[email protected]>, from
Yes, but remember 'there's (a new) one born every minute'. Or these
days, probably every 30 seconds.
I'm fed up with the pseudo experts who point their fingers at anything other
then people who at some point have to take responsibility for the
technology they use. Just think where we'd be if "experts" took that
position when Henry Ford introduced that thing called a Model T. We'd still
be blaming him for every auto accident that ever happened and we all be
dependent on some "expert" to drive us around.
As with any advancement in our history, our society has had to learn how to
use it responsibly. The only thing I agree with is that there will always
be stupid users like there will always be stupid drivers but I certainly
don't blame Ford, Chevy, or any other auto manufactures for these drivers
stupidity.
What I'm really fed up with is so called experts trying to protect their
importance (and inflate their egos) by NOT teaching users basic things about
the technology they use. They claim it's useless but what its is really all
about is job security. They're afraid they may suffer the same fate as the
TV repairman.
On Tue, 12 Aug 2003 20:57:29 -0400, "Robert R Kircher, Jr."
Your solution is to tell people to use av software and a firewall,
right? This newsgroup is frequented almost daily with people who use
av software and a firewall and are screaming for help with some virus
they got nailed with. Your level of education is going to to have to
extend far beyond that. In fact, I was just exchanging emails with a
very knowledegeable guy on virus matters who was behind a firewall and
had even disabled some unnecessary Win 2K internet services who got
nailed by the subject malware.
Users who get nailed are not necessarily stupid at all. Your analogies
suck in any event
I'm goddam tired of trying to do mission impossible, I'll tell you
that. As I said, be my guest and beat yoiur head up against the wall.
It takes far more technical savvy to achieve a decent level of
security than I think you imagine. And the vast majority of PC users
don't have the technical background.
What's needed are far more secure OS and apps right out of the box
which means less features. Whether or not such a balance will be
achieved remains to be seen.
Howdy -- can't find it!?
[tk@hybris:~]$ wget
ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2003-011.txt
--01:18:05--
ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2003-011.txt
=> `NetBSD-SA2003-011.txt'
Resolving ftp.netbsd.org... done.
Connecting to ftp.netbsd.org[204.152.184.75]:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/NetBSD/security/advisories ... done.
==> PORT ... done. ==> RETR NetBSD-SA2003-011.txt ...
No such file `NetBSD-SA2003-011.txt'.
Is this the issue regarding Realpath(3)?
No-one releases perfect code, least of all 100% of the time, but I'm
more than happy to put my trust into a group that produce much higher
quality in code than M$...
Somewhere along the line the consumer has to take on some responsibility.
In this case MS release a fix over a month ago. At that point it's up to
the user to do there part of the deal and use common since and update their
systems. (or in this case at least have a firewall).
Just think where we'd be if "experts" took that
position when Henry Ford introduced that thing called a Model T. We'd still
be blaming him for every auto accident that ever happened and we all be
dependent on some "expert" to drive us around.
As with any advancement in our history, our society has had to learn how to
use it responsibly.
hey guys, just tried to install the thingy from Microsoft,
i select my system language in the checkbox of the download,
download and get a message that the download would not
match my systems language.
you guys make it sound so easy....
<sigh>
I missed the ".asc" at the end of the line, because of the word wrap
in the article (een without that .asc it went over three lines of
text)
At least *some* realpath() issue. I can only report the article, but
don't completely understand it. It seems to allow access to areas
that should have been off limits.
I can understand this, the only problem with *this* bug is that it is
very fundamental, and present in all versions of BSD before May 22nd.
But they are much more eager to fix it, once the vulnerability is
found. I wish MS were that fast.