public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lauri.love at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/15014] gethostbyname_r() returns EINVAL (22) instead of ERANGE (34) (CVE-2015-0235)
Date: Tue, 27 Jan 2015 23:41:00 -0000	[thread overview]
Message-ID: <bug-15014-131-TagEriSC0W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15014-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15014

nsh <lauri.love at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lauri.love at gmail dot com

--- Comment #3 from nsh <lauri.love at gmail dot com> ---
Right, obviously this is with all due deference and respect and I hope nobody
takes it the wrong way and thinks I'm being a dick or anything, but: 

Could we take this moment and look back maybe somewhat systematically over
other closed bugs that were deemed of low importance and no security impact
which involved very clearly increasing the size of a buffer so that it becomes
big enough to not get overflowed? 

This could save a lot on a lot of shitty logo design and hot air and generally
silliness in the future...

Best, 
nsh

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-01-27 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 21:41 [Bug network/15014] New: gethostbyname_r() returns EINVAL (22) instead of ERANGE (34) peter.klotz99 at gmail dot com
2013-04-15 11:33 ` [Bug network/15014] " siddhesh at redhat dot com
2013-04-15 13:02 ` siddhesh at redhat dot com
2013-05-21 10:57 ` schwab@linux-m68k.org
2014-06-13 19:04 ` fweimer at redhat dot com
2015-01-27 15:07 ` [Bug network/15014] gethostbyname_r() returns EINVAL (22) instead of ERANGE (34) (CVE-2015-0235) fweimer at redhat dot com
2015-01-27 23:41 ` lauri.love at gmail dot com [this message]
2015-01-28  1:59 ` joseph at codesourcery dot com
2015-01-28 12:10 ` lauri.love at gmail dot com
2021-11-30  9:14 ` ma.ro.so01234567890 at gmail dot com

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=bug-15014-131-TagEriSC0W@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).