mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>, Dan Kegel <dank@kegel.com>,
	Xavier Bestel <xavier.bestel@free.fr>,
	Andrey Borzenkov <arvidjaar@mail.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: Relax permissions for reading hard drive serial number?
Date: Sun, 2 Dec 2007 18:43:33 +0200	[thread overview]
Message-ID: <20071202164333.GJ6372@mea-ext.zmailer.org> (raw)
In-Reply-To: <200711292207.46967.bzolnier@gmail.com>

On Thu, Nov 29, 2007 at 10:07:46PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > There are people who, for privacy reasons, really don't like that "unique"
> > unchangeable serial numbers can be retrieved by untrusted users.
> > 
> > You should probably chmod the file on the users system, if he is fine with
> > that, but not change the kernel default.
> 
> Seconded.
> 
> While on it, how's about exporting model/firmware/serial through
> sysfs so /proc/ide/hd*/identify don't have to be used?


Nice, except that while my home workstation running 2.6.23 kernel
does have 4 SATA disks in it, plus a compact flash memory card on
PATA (boot device, while SATA-disks are JBOD in SW RAID), it has
_no_  /sys/bus/ide/,  nor  /proc/ide/
All devices are under /sys/bus/scsi/

Simplest way for me to pick this data is to use  "hdparm -I /dev/sdX"
command.  Which of course must be run as root.  All it does is to open
named device, and issue one ioctl().

That ioctl() can be embedded into a suid-root helper program, or it
can even (in case of Wine) be run separately to write a text file
storing these identifier data on some Wine config file, which the
"read from physical device X" then does receive.

In my case I don't want to report any of the hard-drive serial numbers,
but rather my boot-device - a flash drive.  Hard-drives do break at
some point in time, a flash drive in read-only mode does last considerably
longer.

> [PATCH] ide: add /sys/bus/ide/devices/*/{model,firmware,serial} sysfs entries
...

/Matti Aarnio

  reply	other threads:[~2007-12-02 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 15:13 Dan Kegel
2007-11-29 15:37 ` Xavier Bestel
2007-11-29 15:46   ` Dan Kegel
2007-11-29 17:39     ` Kay Sievers
2007-11-29 21:07       ` Bartlomiej Zolnierkiewicz
2007-12-02 16:43         ` Matti Aarnio [this message]
2007-12-02 18:45     ` Matti Aarnio
2007-12-04 12:06       ` Kyle Moffett
2007-12-02 14:15 ` Pavel Machek

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=20071202164333.GJ6372@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=arvidjaar@mail.ru \
    --cc=bzolnier@gmail.com \
    --cc=dank@kegel.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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®