From: "javanthropus (Jeremy Bopp) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "javanthropus (Jeremy Bopp)" <noreply@ruby-lang.org>
Subject: [ruby-core:119537] [Ruby master Bug#20802] It is possible to set the encoding of an IO instance to one that requires binmode when binmode is not set
Date: Mon, 21 Oct 2024 08:50:11 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20802.20241017134255.692@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20802.20241017134255.692@ruby-lang.org>
Issue #20802 has been reported by javanthropus (Jeremy Bopp).
----------------------------------------
Bug #20802: It is possible to set the encoding of an IO instance to one that requires binmode when binmode is not set
https://bugs.ruby-lang.org/issues/20802
* Author: javanthropus (Jeremy Bopp)
* Status: Open
* ruby -v: ruby 3.3.4 (2024-07-09 revision be1089c8ec) [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
I don't know what problems this may cause, but there are guards against setting the encoding of an IO instance to one such as UTF-16LE when the IO instance is not set to binary mode. Here is a method to bypass those guards:
```ruby
f1 = File.open('/dev/null')
f2 = File.open('/dev/null')
f1.binmode
f1.set_encoding('utf-16le')
f2.set_encoding('utf-8')
f1.reopen(f2)
f1.binmode? # <= false
f1.external_encoding # <= Encoding::UTF_16LE
```
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
parent reply other threads:[~2024-10-21 8:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <redmine.issue-20802.20241017134255.692@ruby-lang.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=redmine.issue-20802.20241017134255.692@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.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).