public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/31974] glibc incorrectly uses __isoc23_sscanf for C++
Date: Mon, 22 Jul 2024 13:03:20 +0000	[thread overview]
Message-ID: <bug-31974-131-oSJXhfou7O@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31974-131@http.sourceware.org/bugzilla/>

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

--- Comment #26 from cqwrteur <euloanty at live dot com> ---
(In reply to cqwrteur from comment #25)
> (In reply to cqwrteur from comment #24)
> > (In reply to Jonathan Wakely from comment #12)
> > > Try to focus and stay on topic, your irrational hatred of std::format has
> > > nothing to do with this glibc PR. (But it doesn't have the same issue,
> > > because it's header-only so can very easily tailor which format specifiers
> > > are supported based on the current value of __cplusplus, you're mistaken as
> > > usual.)
> > 
> > irrational hatred? Do you even know how many security vulnerabilities were
> > caused by format string and std::format is also very slow and bloated. It is
> > even much slower than stream. And it breaks abi. It causes trouble for
> > compilers to sanitize the imports.
> > 
> > 
> > https://gist.github.com/Au-lit/447f376101674503aac2d721fcee0cd1
> > 
> > How are those points irrational?
> 
> santize the inputs

What Are Format String Vulnerabilities?

https://www.invicti.com/blog/web-security/format-string-vulnerabilities/

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

  parent reply	other threads:[~2024-07-22 13:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 12:45 [Bug string/31974] New: " euloanty at live dot com
2024-07-13 12:45 ` [Bug string/31974] " euloanty at live dot com
2024-07-13 13:58 ` euloanty at live dot com
2024-07-13 15:08 ` sam at gentoo dot org
2024-07-13 19:31 ` pinskia at gcc dot gnu.org
2024-07-14  0:25 ` euloanty at live dot com
2024-07-14  1:14 ` pinskia at gcc dot gnu.org
2024-07-14  8:04 ` jwakely.gcc at gmail dot com
2024-07-15  8:25 ` euloanty at live dot com
2024-07-15  8:27 ` euloanty at live dot com
2024-07-15  8:33 ` euloanty at live dot com
2024-07-15  9:02 ` euloanty at live dot com
2024-07-15 10:21 ` schwab@linux-m68k.org
2024-07-22  9:37 ` jwakely.gcc at gmail dot com
2024-07-22 12:22 ` euloanty at live dot com
2024-07-22 12:25 ` jwakely.gcc at gmail dot com
2024-07-22 12:25 ` euloanty at live dot com
2024-07-22 12:27 ` jwakely.gcc at gmail dot com
2024-07-22 12:29 ` euloanty at live dot com
2024-07-22 12:32 ` euloanty at live dot com
2024-07-22 12:33 ` jwakely.gcc at gmail dot com
2024-07-22 12:43 ` adhemerval.zanella at linaro dot org
2024-07-22 12:44 ` euloanty at live dot com
2024-07-22 12:46 ` jwakely.gcc at gmail dot com
2024-07-22 12:47 ` jwakely.gcc at gmail dot com
2024-07-22 12:47 ` jwakely.gcc at gmail dot com
2024-07-22 12:50 ` adhemerval.zanella at linaro dot org
2024-07-22 12:53 ` euloanty at live dot com
2024-07-22 12:54 ` euloanty at live dot com
2024-07-22 12:57 ` euloanty at live dot com
2024-07-22 13:00 ` euloanty at live dot com
2024-07-22 13:01 ` euloanty at live dot com
2024-07-22 13:03 ` euloanty at live dot com [this message]
2024-07-22 13:08 ` adhemerval.zanella at linaro dot org
2024-07-22 13:08 ` adhemerval.zanella at linaro dot org
2024-07-22 13:12 ` euloanty at live dot com
2024-07-22 13:21 ` euloanty at live 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-31974-131-oSJXhfou7O@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).