public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Sat, 03 Dec 2011 21:10:48 -0500	[thread overview]
Message-ID: <4EDAD6A8.3040805@orlitzky.com> (raw)
In-Reply-To: <CAN0CFw38oqPKLU5-+W=C7aa5jfGi7_Tkdx7CQdznvMWZwR7cog@mail.gmail.com>

On 12/03/2011 08:57 PM, Grant wrote:
>>> Very cool.  I found out clamscan and avgfree scan the filesystem so I
>>> thought I should set it up, but if it's not necessary I won't bother.
>>> All of my mail users are on Gentoo so do I need to bother having
>>> clamav scan my incoming mail?
>>
>>
>> Well, they aren't going to get infected with anything, but ClamAV could
>> still keep the virus message (which is obviously unwanted) out of their
>> inbox. There are also some third-party signatures[1] for ClamAV that catch
>> scam/phishing mail.
>
> There is info on Linux viruses here:
>
> http://en.wikipedia.org/wiki/Linux_malware
>
> I shouldn't be concerned about that?
>

The "big" risk (although still negligible) is that someone will mail 
your users an executable that does something bad. But, you would have to 
save it under /home, chmod +x it, and then run it manually for it to be 
dangerous.

If you use portage to install packages, you should not ever need to 
chmod +x anything. It's a big red flag and normal users don't even need 
to know how to do it.

Mount /home noexec for extra safety.

Note that antivirus wouldn't help anyway if your users are going to do 
whatever the email says without question =)



  reply	other threads:[~2011-12-04  2:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 19:52 [gentoo-user] clamav and spamassassin Grant
2011-12-03 22:54 ` Michael Orlitzky
2011-12-04  0:59   ` Grant
2011-12-04  1:35     ` Michael Orlitzky
2011-12-04  1:57       ` Grant
2011-12-04  2:10         ` Michael Orlitzky [this message]
2011-12-04  1:59   ` Pandu Poluan
2011-12-04  2:17     ` Michael Orlitzky
2011-12-04  2:48       ` Pandu Poluan
2011-12-04  3:06         ` Michael Orlitzky
2011-12-04  8:27           ` Pandu Poluan
2011-12-06  0:15       ` Grant
2011-12-06  0:45         ` Pandu Poluan
2011-12-06  0:52           ` Michael Orlitzky
2011-12-06  1:01             ` Pandu Poluan
2011-12-06  1:14               ` Michael Orlitzky
2011-12-06  3:24             ` Grant
2011-12-06  4:43               ` Michael Orlitzky
2011-12-06 16:32                 ` Grant
2011-12-06 17:11                   ` Michael Orlitzky
2011-12-06 19:17                     ` Paul Hartman
2011-12-07  0:16                       ` Pandu Poluan
2011-12-06 21:34                     ` Grant
2011-12-06 22:20                       ` Michael Orlitzky
2011-12-07  1:02                         ` Grant
2011-12-07 16:38                           ` Michael Orlitzky
2011-12-07 18:16                             ` Grant
2011-12-07 18:56                               ` Michael Orlitzky
2011-12-07 19:00                                 ` Michael Orlitzky
2011-12-08  0:49                                 ` Grant
2011-12-07  9:15                         ` Pandu Poluan
2011-12-07 16:01                           ` Grant
2011-12-07 16:47                             ` Pandu Poluan
2011-12-07  0:57                     ` Grant
2011-12-07  1:11                       ` Pandu Poluan
2011-12-07 16:34                       ` Michael Orlitzky
2011-12-07 18:08                         ` Grant

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=4EDAD6A8.3040805@orlitzky.com \
    --to=michael@orlitzky.com \
    --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