| 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
| ||
|
Message-ID: <CADmzSShVE9PNc+imVakhDfp-+nfga59kbKczAgKomiu94ayn8g@mail.gmail.com> Date: Tue, 20 Dec 2011 17:50:02 -0600 From: Carl Karsten <carl@...sonnelware.com> To: Stefan Richter <stefanr@...6.in-berlin.de> 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 Tue, Dec 20, 2011 at 5:43 PM, Stefan Richter <stefanr@...6.in-berlin.de> wrote: > On Dec 21 Stefan Richter wrote: >> 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. > > Or > (cd /sys/bus/firewire/devices; grep . $(ls -c */guid)) | sed s/\\/guid:/\\t/ > > for a list in reverse-chronological order of discovery. > Same but narrowed down to AV/C devices: > > (cd /sys/bus/firewire/devices; for fw in $(grep 0x00a02d:0x010001 $(ls -c */units) | cut -f1 -d/); do printf $fw\\t; cat $fw/guid; done) To further describe my pain: I am going to run dmesg anyway to see if the device is being detected and or any errors. Once I see that it is connected, it is really nice having the guid right there. I am really bummed I didn't invite you to PyCon in Leipzig so you could see what I do first hand. Maybe next time. -- Carl K -- 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/
Powered by blists - more mailing lists