From: "Josh" <jlamb03@elitemail.org>
To: linux-admin@vger.kernel.org
Subject: unauthorized access
Date: Tue, 11 May 2004 14:14:58 -0700 [thread overview]
Message-ID: <1084310098.28632.196278681@webmail.messagingengine.com> (raw)
Hello,
I am having a problem. Someone in my workplace downloaded many files,
some porn onto my user directory. I was framed for it, and eventually
the matter was settled but it is still not known who committed this act.
I want to find out who was able to bypass permissions and save these
files into my directory. I am sorry to say that my workplace uses a
windows system, so it couldn't just be "root"! Are there any recommended
log generators that I can use to discreetly monitor if my account is
being accessed and where from. Somehow the perpetrator was able to make
it seem as if I had logged on as someone else, but saved the files into
my directory. I know you guys can solve it, after all we are linux users!
Thanks for the help,
Josh
--
http://www.fastmail.fm - Access all of your messages and folders
wherever you are
next reply other threads:[~2004-05-11 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 21:14 Josh [this message]
2004-05-12 14:00 ` unauthorized access Viliam Kocinsky
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 20:53 Josh
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=1084310098.28632.196278681@webmail.messagingengine.com \
--to=jlamb03@elitemail.org \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).