Bugtraq mailing list archives
Re: bug in minicom 1.75 ?
From: chrish () DEBIAN ORG (Christian Hudon)
Date: Mon, 31 Aug 1998 20:14:41 -0400
--xaMk4Io5JJdpkLEb Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Sunday, August 30, Koji wrote
Hi all. =20
[snip]
# minicom `perl -e 'print "0" x 1000;'` Segmentation fault (core dumped) =20
On Debian 2.0 (minicom 1.75-3), I get the following results: chrish@pianocktail:[~] >minicom `perl -e 'print "0" x 1000;'` Sorry 00000000000000000000000000000. You are not allowed to use configurati= on 000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000000000000000000000000000000000000000000000000000000000000= 000000000000000000 Ask your sysadm to add your name to /etc/minicom.users Also, minicom is not installed setuid/setgid on Debian. (If you want someon= e=20 to have access to your modem for dialing out, you add them to the dialout group.) Christian --xaMk4Io5JJdpkLEb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBNes8cI4/+LDuJkz5AQGR5gP/Z+qzbsgIeIMdFdM+ba1tgEpOWXs1XYfj 6V9j5yCgjbBmPq5QhftuEH7+nVoXshsPZlpFfllAHCWB+pq96cRnr3Fv/UHxiQmi Jnrc9BB/8EgujkCyk16XY+xCV5j1KHr5E9EGEfybR2qiNdIEzXer+NP5n/oUK2z3 L66fR7YPyY8= =SaVY -----END PGP SIGNATURE----- --xaMk4Io5JJdpkLEb--
Current thread:
- Re: bug in minicom 1.75 ? Christian Hudon (Aug 31)
- <Possible follow-ups>
- Re: bug in minicom 1.75 ? Scott Stone (Aug 31)