From: Yuri Csapo <ycsapo@exchange.mines.edu>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: "spontaneous" permissions changes
Date: Wed, 26 Aug 2009 15:08:26 -0600 [thread overview]
Message-ID: <4A95A44A.50305@exchange.mines.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
Hi all, I have a strange situation I wish someone could help me with. This is the setup:
- Virtual machine running the latest VM under ESXi
- VM has one processor, 2 GB RAM, 1 GB swap
- Ubuntu 8.04 LTS
- The virtual host runs only this VM
- Virtual host connects to a Lefthand Networks (now HP) SAN through 1 GB copper ethernet and iSCSI
- VM has a 1 TB volume from the SAN that looks like a SCSI drive to Linux (/dev/sdc)
- sdc is formatted as one big ext3 partition (sdc1)
- sdc1 is exported both as an NFS resource and a SMB share (via Samba)
- Authentication is Kerberos and authorization is local, if that matters
The permissions on that partition's mount point, usually 755, changed suddenly to 400. I have looked
at sudo logs, root's and all admins' history files and I can find no evidence of someone changing
those permissions or of tampering with the logs.
Physical access to the box requires the right keycard; logon (ssh) access to the box is restricted
to sysadmins and support personel only; the root password is a 32 char long random string that lives
in an encrypted repository on my iPod Touch. There are only 2 people, myself included, with full
sudo rights; there are another 5 people with sudo rights to a number of administration things
including chmod.
This is a state university and it happened on the first day of classes.
My questions:
- Did I look everywhere I should be looking to find evidence of foul play?
- Does anyone know of anything in this setup that could trigger a seemingly spontaneous permissions
change like that?
Thanks,
--
Yuri Csapo
Academic Computing & Networking
Colorado School of Mines
CT-256
Phone: (303) 273-3503
Fax: (303) 273-3475
Email: ycsapo@mines.edu
Please use the following link to open a service request:
http://helpdesk.mines.edu
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
[-- Attachment #2: ycsapo.vcf --]
[-- Type: text/x-vcard, Size: 200 bytes --]
begin:vcard
fn:Yuri Csapo
n:Csapo;Yuri
org:Colorado School of Mines;CCIT
email;internet:ycsapo@mines.edu
title:System Administrator
tel;work:(303) 273-3503
x-mozilla-html:FALSE
version:2.1
end:vcard
next reply other threads:[~2009-08-26 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 21:08 Yuri Csapo [this message]
2009-08-26 21:56 ` "spontaneous" permissions changes Rick
2009-08-27 20:22 ` Yuri Csapo
2009-08-27 8:45 ` Franck RICHARD
2009-08-27 20:25 ` Yuri Csapo
[not found] ` <fff5b0760908271401r3b32aacbne8d23f44871aa56a@mail.gmail.com>
[not found] ` <78B73E114B5F754087DF95C2C6B640531A4EC45C79@MAILBOXCCR.monext.net>
2009-08-28 14:09 ` Yuri Csapo
[not found] ` <830324620908270522q5582262bsf59187357f269d23@mail.gmail.com>
2009-08-27 20:30 ` Yuri Csapo
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=4A95A44A.50305@exchange.mines.edu \
--to=ycsapo@exchange.mines.edu \
--cc=linux-admin@vger.kernel.org \
--cc=ycsapo@mines.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).