public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gurtmistrioty90 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/19519] iconv(1) with -c option hangs on illegal multi-byte sequences (CVE-2016-10228)
Date: Mon, 26 Jul 2021 07:27:51 +0000 [thread overview]
Message-ID: <bug-19519-131-LZHEhclSRZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19519-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19519
gurtmistrioty <gurtmistrioty90 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gurtmistrioty90 at gmail dot com
--- Comment #39 from gurtmistrioty <gurtmistrioty90 at gmail dot com> ---
Users are recommended to enable the Quality of Service feature to allow their
device to assign priority to web applications, Internet streaming, and other
prominent services. While configuring the QoS in a Netgear router through the
routerlogin.net interface, a user is prompted to mention the upload and
download Internet bandwidth in the provided field. You can take help of the
Speedtest feature to determine the upload and download Internet speed of your
router.
https://netgeargenierouter.net/
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-26 7:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19519-131@http.sourceware.org/bugzilla/>
2020-06-03 9:05 ` joshfeild9281 at gmail dot com
2020-07-08 15:55 ` arjun.is at lostca dot se
2020-07-08 16:03 ` arjun.is at lostca dot se
2020-07-08 16:42 ` jsm28 at gcc dot gnu.org
2020-07-09 20:43 ` fweimer at redhat dot com
2020-08-12 3:21 ` vincent-srcware at vinc17 dot net
2020-08-25 9:50 ` arjun.is at lostca dot se
2020-08-25 9:57 ` arjun.is at lostca dot se
2020-10-20 15:23 ` arjun.is at lostca dot se
2021-03-10 11:31 ` ivankamalikova50 at gmail dot com
2021-05-06 6:48 ` tustazolto at biyac dot com
2021-05-10 7:47 ` hawex77340 at cnxingye dot com
2021-05-10 7:48 ` hawex77340 at cnxingye dot com
2021-05-10 7:48 ` hawex77340 at cnxingye dot com
2021-05-12 7:14 ` routerlognet at gmail dot com
2021-05-12 11:55 ` yerisok983 at o3live dot com
2021-05-25 3:38 ` ampva300 at gmail dot com
2021-05-27 12:33 ` routerlognet at gmail dot com
2021-07-02 7:27 ` spanksaucee01 at gmail dot com
2021-07-14 6:26 ` stokesandrew.sa at gmail dot com
2021-07-14 7:57 ` vincent-srcware at vinc17 dot net
2021-07-15 11:03 ` stokesandrew.sa at gmail dot com
2021-07-15 11:03 ` stokesandrew.sa at gmail dot com
2021-07-16 12:12 ` stokesandrew.sa at gmail dot com
2021-07-20 5:15 ` sophia.paxton23 at gmail dot com
2021-07-20 9:11 ` extenderslinksys195 at gmail dot com
2021-07-21 10:07 ` extenderslinksys195 at gmail dot com
2021-07-26 7:27 ` gurtmistrioty90 at gmail dot com [this message]
2021-08-13 22:39 ` technicalexpertshelp at gmail dot com
2021-08-13 22:41 ` technicalexpertshelp at gmail dot com
2021-08-23 15:49 ` studyhardarvind at gmail dot com
2021-08-23 15:49 ` studyhardarvind at gmail dot com
2021-08-26 12:07 ` mywifiextender7 at gmail dot com
2021-09-02 11:44 ` languagefluent2 at gmail dot com
2021-09-15 2:21 ` namboru at jasaseo dot one
2021-09-22 4:15 ` linksysroutersetup0 at gmail dot com
2021-09-22 20:40 ` gullyboy693 at gmail dot com
2021-09-22 20:40 ` gullyboy693 at gmail dot com
2021-10-19 21:30 ` gullyboy693 at gmail dot com
2021-10-25 16:43 ` studyhardarvind at gmail dot com
2021-11-10 13:48 ` routerlogin07 at gmail dot com
2021-11-15 17:07 ` studyhardarvind at gmail dot com
2021-11-15 17:09 ` studyhardarvind at gmail dot com
2022-02-24 6:55 ` extenderslinksys195 at gmail dot com
2022-02-24 6:56 ` extenderslinksys195 at gmail dot com
2022-03-29 14:51 ` gullyboy693 at gmail dot com
2022-05-24 5:46 ` extenderslinksys195 at gmail dot com
2022-05-24 5:47 ` extenderslinksys195 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-19519-131-LZHEhclSRZ@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).