From: "Mike A. Harris" <mharris@opensourceadvocate.org>
To: Syd Polk <spolk@redhat.com>
Cc: Fernando Nasser <fnasser@cygnus.com>, insight@sources.redhat.com
Subject: Re: Buffer Overflow Patch in GDB/TCL Interface code.
Date: Thu, 19 Oct 2000 17:50:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0010191820400.859-100000@asdf.capslock.lan> (raw)
In-Reply-To: <39EF1F66.6D763F7F@redhat.com>
On Thu, 19 Oct 2000, Syd Polk wrote:
>Date: Thu, 19 Oct 2000 09:20:54 -0700
>From: Syd Polk <spolk@redhat.com>
>To: Fernando Nasser <fnasser@cygnus.com>
>Cc: insight@sources.redhat.com
>Content-Type: text/plain; charset=us-ascii
>Subject: Re: Buffer Overflow Patch in GDB/TCL Interface code.
>
>My only concern is whether this call, asprintf, is available on all platforms.
>
IMHO, calls to any functions such as this, are just oddball
memleak situations waiting to happen. I've never heard of
asprintf before myself.. Shouldn't it also be asnprintf() to
avoid a potential overflow? Sorry if not, as I haven't looked at
the actual usage in the code. Just some thoughts to share..
Take care!
TTYL
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open source advocate
Computer Consultant - Capslock Consulting
Copyright 2000 all rights reserved
----------------------------------------------------------------------
If you're interested in computer security, and want to stay on top of the
latest security exploits, and other information, visit:
http://www.securityfocus.com
next prev parent reply other threads:[~2000-10-19 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 6:30 Fernando Nasser
2000-10-19 9:17 ` Syd Polk
2000-10-19 9:27 ` Fernando Nasser
2000-10-19 11:26 ` Syd Polk
2000-10-20 8:42 ` Liberty, asprintf(), malloc() Fernando Nasser
2000-10-19 17:50 ` Mike A. Harris [this message]
[not found] <39EE5ED1.2CDECCDB@ozemail.com.au>
2000-10-19 6:20 ` Buffer Overflow Patch in GDB/TCL Interface code Fernando Nasser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0010191820400.859-100000@asdf.capslock.lan \
--to=mharris@opensourceadvocate.org \
--cc=fnasser@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=spolk@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).