linux-kernel - Re: [PATCH 1/3] firewire: do not expose globally unique IDs in the kernel log

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111221001031.539ef397@stein>
Date:	Wed, 21 Dec 2011 00:10:31 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Carl Karsten <carl@...sonnelware.com>
Cc:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] firewire: do not expose globally unique IDs in the
 kernel log

On Dec 20 Carl Karsten wrote:
> grumble.
> 
> I use those guids like so:
> 
> plug in dv cam, dmesg, cut guid to clipboard, run:
> dvgrab -guid (paste)

How about:

	#!/bin/sh
	guid=$(cat /sys/bus/firewire/devices/$1/guid)
	shift
	dvgrab -guid $guid "$@"

To be called as "dvgrab-wrapper fw3 [more dvgrab options]", with fw3 being
the device of your choice, e.g. the one that just scrolled by in syslog.

Or you run "grep . /sys/bus/firewire/devices/*/guid | sed s/\\/guid:/\\t/"
before dvgrab, and you get a list of GUIDs from which you can copy and
paste.

> It also kinda helps me keep track of what devices are misbehaving, but
> this alone isn't very important.
> 
> Any chance of making this configurable?

So far the configuration of the "new" firewire drivers were kept at an
essential minimum, and I am hesitant to add more baroque ones.  I would
rather drop this patch now that there was negative feedback, unless there
is going to be positive feedback as well.
-- 
Stefan Richter
-=====-==-== ==-- =-=--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/