full-disclosure - Re: Full-Disclosure Digest, Vol 7, Issue 25

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.50.0509151242460.29648-100000@kegger.national-security.net>
Date: Thu Sep 15 21:09:00 2005
From: fd at ew.nsci.us (fd@...nsci.us)
Subject: Re: Full-Disclosure Digest, Vol 7, Issue 25

On Wed, 14 Sep 2005, Peer Janssen wrote:
> I never found information about the following recurrent question of mine 
> either:
> If a plug in an USB storage device, it has a /dev/sg<...> assigned to 
> it. But which one? I need to know this mapping in order to mount it. I 
> always deduce this device's name from the syslog, which works but is a 
> bit of a PITA, so I always wondered if there is no other way to get this 
> info, namely something like lsusb. lsusb, which would be the logical 
> place to look for it, doesn't give away this info, at least not in an 
> easily recognizable form (e.g. I never figured it out). sg_scan and such 
> didn't do the trick for me either, although I might have missed 
> something here.


Write your own lssd?

echo 'dmesg | grep sd[abcdefg]' > /bin/lssd ; chmod 755 /bin/lssg


-- 
Eric Wheeler
Vice President
National Security Concepts, Inc.
PO Box 3567
Tualatin, OR 97062

http://www.nsci.us/
Voice: (503) 293-7656
Fax:   (503) 885-0770