public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jarry <jarry@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  antivirus
Date: Thu, 09 Mar 2006 05:49:56 +0100	[thread overview]
Message-ID: <440FB3F4.9060800@gmx.net> (raw)
In-Reply-To: <FAEEIJPAOFEMBBLKPMJEAENFFBAA.BYoung@NuCORETech.com>

Bob Young wrote:

> PowerUser is different from Admin, Admin is the equevelent of root in the
> Linux/Unix world, PowerUser is not. The primary and most important
> difference is the ability to *write* to the registry, It's perfectly safe to
> routinely log on as a PowerUser, as PowerUsers can *not* write to registry
> keys that affect the entire system, while Admin users can write to *any*
> registry key.

I'm not sure if this is true. Anyway, PowerUser has the ability
to install sw (even system patches!), alter executables and system
files! PowerUser can write to C:\ProgramFiles, or C:\Windows, and
that is exactly, what a virus need to spread itself. Not many viruses
can hide their code in registry (that is just equivalent to /etc in
unix-world), mostly they attach themselves to some exe/sys file,
or overwrite them...

So, if you start a virus-infected program as a PowerUser, there
are perfect conditions for spreading infection. If there were
some virus for linux, and you start it as a normal user, it can
not alter executables in /usr or /sbin, because user does not have
write access to them. Such a virus could infect only *your* files.

I'd say PowerUser is something between a restricted user, and admin.

Jarry
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-03-09  4:54 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
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 [this message]
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=440FB3F4.9060800@gmx.net \
    --to=jarry@gmx.net \
    --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