From: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] antivirus
Date: Thu, 9 Mar 2006 17:12:27 -0000 [thread overview]
Message-ID: <E409A0EB8A569347802C508C49C13439073060@BCV0X134EXC0003> (raw)
In-Reply-To: <FAEEIJPAOFEMBBLKPMJECENDFBAA.BYoung@NuCORETech.com>
> -----Original Message-----
> From: Bob Young [mailto:BYoung@nucoretech.com]
> Sent: 08 March 2006 21:05
> To: gentoo-user@lists.gentoo.org
> Subject: RE: [gentoo-user] antivirus
>
[snip]
> As to <insert App Name here> not running without Admin
> rights, most of those
> cases can be taken care of with RunAs. It's better to run a
> single App with
> Admin privledges rather than have all apps including email
> and browsers
> running with Admin rights.
Actually, it would be better to troubleshoot the particular application
and allow it write/execute or modify rights *only* to the files it needs
to access for the particular plain user (typically some files or a
folder under C:\Program Files).
It may take some time to set up access rights for all such badly written
apps, but it'll keep your M$Windoze box as safe as it will ever be. If
in addition you shut down all the open by default Windoze ports
(135-139, 445, 500, 1900, 4000 + remote admin) and disable
unnecessary/dangerous services and also stop using OE and IE (or at
least stop using them with their default settings) you should be safe
enough going about your normal business.
The above suggestions will ensure that viruses cannot be easily
installed (thus protecting users from clicking idiotically on any
rubbish they happen to receive as an email attachment) and will also
stop most of the trojans scanning the internet for default open Windoze
ports. I know it works - my wife has not had her NT4/WinXP OS infected
since 1998, despite downloading all sort of garbage. Of course, running
Nod32 also helps every now and then, mostly by providing early warnings
about mail attachments.
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-10 4:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 5:55 [gentoo-user] antivirus Ghaith Hachem
2006-03-06 6:08 ` John Jolet
2006-03-06 6:10 ` Masood Ahmed
2006-03-06 6:28 ` Ghaith Hachem
2006-03-06 6:34 ` Boyd Stephen Smith Jr.
2006-03-06 6:50 ` Masood Ahmed
2006-03-06 7:11 ` Alexander Skwar
2006-03-06 7:29 ` Ghaith Hachem
2006-03-06 17:15 ` Hemmann, Volker Armin
2006-03-08 19:40 ` neil
2006-03-08 20:26 ` [gentoo-user] [WAY OT] plural of virus (was antivirus) Willie Wong
2006-03-06 14:16 ` [gentoo-user] Re: antivirus Peter
2006-03-06 14:33 ` Ghaith Hachem
2006-03-06 16:27 ` [gentoo-user] " Peter
2006-03-06 18:26 ` [gentoo-user] antivirus Jarry
2006-03-07 3:03 ` jed mallen
2006-03-08 19:23 ` neil
2006-03-08 19:31 ` Tim Igoe
2006-03-08 20:24 ` Bob Young
2006-03-08 20:36 ` John Jolet
2006-03-08 21:04 ` Bob Young
2006-03-09 17:12 ` Michael Kintzios [this message]
2006-03-10 18:14 ` Bob Young
2006-03-08 21:03 ` Jarry
2006-03-08 21:19 ` Bob Young
2006-03-09 4:32 ` Ghaith Hachem
2006-03-09 19:35 ` Tim Igoe
2006-03-09 21:10 ` Bob Young
2006-03-09 4:49 ` Jarry
2006-03-09 16:09 ` Bob Young
2006-03-15 9:56 ` Midnight Toker
2006-03-15 17:59 ` Bob Young
2006-03-15 9:53 ` Midnight Toker
[not found] ` <1755830.1141669569249.JavaMail.root@sniper5>
2006-03-13 20:59 ` Justin Krejci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E409A0EB8A569347802C508C49C13439073060@BCV0X134EXC0003 \
--to=michaelkintzios@lycos.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox