From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: Is there something that can be done against this ???
Date: Tue, 14 Aug 2001 09:34:52 -0700 (PDT) [thread overview]
Message-ID: <20010814163452.3046E783F5@mail.clouddancer.com> (raw)
In-Reply-To: <9lb8vp$10q$1@ns1.clouddancer.com>
In-Reply-To: <NOEJJDACGOHCKNCOGFOMKENKDCAA.davids@webmaster.com> <3B7924C7.31923A8@trader.com> <9lb8vp$10q$1@ns1.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>
>David Schwartz wrote:
>>
>> > The question is not : "is this script dangerous ?",
>> > but "are you ready to blindly execute a shell script
>> > (or any program) that you receive in your mail ?".
>>
>> Sure, as a user created solely for that purpose, it should be entirely
>> safe.
>>
>
>How many users are there that use a specific user account to read
>their emails on their Linux workstation ?
>I don't, I use my account to read mails, write documents,
>develop programs,etc. So even if a malicious program does
>not do any arm to the system, it can at least destroy or corrupt my
>own files and I will loose time restoru=ing from last backup and
>rebuilding recently modified files.
Anybody that can think probably does that. First they think that
setting up a test user takes a few seconds, then they think that
restoring from backup takes at least 100x longer....
--
Windows 2001: "I'm sorry Dave ... I'm afraid I can't do that."
next prev parent reply other threads:[~2001-08-14 18:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 1:24 S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-13 1:41 ` Paul G. Allen
2001-08-13 5:12 ` Christopher Abbey
2001-08-13 12:34 ` Alan Cox
2001-08-13 15:18 ` Eric S. Raymond
2001-08-13 15:46 ` Alan Cox
2001-08-13 15:52 ` Eric S. Raymond
2001-08-13 16:00 ` Alan Cox
2001-08-13 18:56 ` Is there something that can be done against this ??? Mircea Ciocan
2001-08-13 19:19 ` Jakob Østergaard
2001-08-13 19:19 ` Ulrich Drepper
2001-08-13 19:20 ` Mircea Ciocan
2001-08-13 19:41 ` Aaron Lehmann
2001-08-13 19:53 ` Chris Meadors
2001-08-13 20:09 ` Admin Mailing Lists
2001-08-13 22:01 ` Rik van Riel
2001-08-14 8:12 ` Helge Hafting
2001-08-13 19:24 ` Peter T. Breuer
2001-08-13 19:34 ` Eli Carter
2001-08-13 19:32 ` Ben Collins
2001-08-13 19:48 ` Ronald Jeninga
2001-08-13 20:02 ` Richard B. Johnson
2001-08-14 8:02 ` Henning P. Schmiedehausen
2001-08-14 8:16 ` joseph.bueno
2001-08-14 10:00 ` David Schwartz
2001-08-14 12:42 ` Helge Hafting
2001-08-14 17:10 ` David Schwartz
2001-08-14 13:16 ` joseph.bueno
2001-08-14 16:34 ` Colonel [this message]
2001-08-15 9:08 ` Helge Hafting
2001-08-14 17:47 ` Scott Wood
2001-08-14 21:27 ` S2464 (K7 Thunder) hangs -- some lessons learned Eric S. Raymond
2001-08-14 22:13 ` Alan Cox
2001-08-14 1:45 ` Paul G. Allen
2001-08-13 20:00 Is there something that can be done against this ??? Per Jessen
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=20010814163452.3046E783F5@mail.clouddancer.com \
--to=klink@clouddancer.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®