Hi Josh and Marco, I'm hereby transmitting Josua's answer to the correct bugreport, please follow up on the separate bugreports.
This is for #591761: > > And unless I am missing something, the usage of /tmp/gsmmodem_* is > > insecure (if confirmed, please clone the bug and contact the security > > team). And expected to *not* work at boot time. And subject to races. > > And just plain ugly. What did the author think? > > I thought I'd make the life easier for users. And yes, it is a quick > hack. > > Maybe you can advise me here too: > > These switchable modems often expose more than one vendor class > interface. If a serial driver is bound to them, each results in a > ttyUSB device. Usually only one of them - which has a transfer type > of "interrupt" - is suitable for the actual connection. Some have > more of these interrupt interfaces though; empiric knowledge says > the lower interface number is right. > > My hack made udev create a symlink to the lowest interrupt interface > after mode-switching. To handle the switched device exclusively > (i.e. leaving any existing devices alone), I am storing just the > bus/device number in the temporary file name. > > I did this only because I found no immediate way to signal > information from one udev RUN to the next; I'd be happy to scrap the > temporary file if it could be done via something like an environment > variable (but I tried that already). > > I would *really* welcome any tips regarding a better way ... -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
