From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bug 206761] New: escape codes in network interface names causes chaos
Date: Thu, 5 Mar 2020 08:05:35 -0800 [thread overview]
Message-ID: <20200305080535.59ff59b0@hermes.lan> (raw)
In-Reply-To: <bug-206761-100@https.bugzilla.kernel.org/>
On Thu, 05 Mar 2020 10:42:39 +0000
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=206761
>
> Bug ID: 206761
> Summary: escape codes in network interface names causes chaos
> Product: Networking
> Version: 2.5
> Kernel Version: 5.6
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: george.shuklin@gmail.com
> Regression: No
>
> netlink permits creation of interfaces with escape codes. Suck names can trick
> root by drawing at random places in terminal.
>
>
> Minimal proof of concept:
>
>
> echo -e '\x1B[2J'|xargs -I I ip link add I type dummy
> ip l
>
>
> (rollback): echo -e '\x1B[2J'|xargs -I I ip link del I
>
My opinion is that this is not a problem that can be addressed without breaking kernel ABI.
parent reply other threads:[~2020-03-05 16:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-206761-100@https.bugzilla.kernel.org/>]
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=20200305080535.59ff59b0@hermes.lan \
--to=stephen@networkplumber.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.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 NNTP newsgroup(s).