From: Eli Zaretskii <eliz@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: 46342@debbugs.gnu.org
Subject: bug#46342: 28.0.50; socks-send-command munges IP address bytes to UTF-8
Date: Tue, 09 Feb 2021 18:14:29 +0200 [thread overview]
Message-ID: <831rdpkyl6.fsf@gnu.org> (raw)
In-Reply-To: <874kils22e.fsf@neverwas.me> (jp@neverwas.me)
> From: "J.P." <jp@neverwas.me>
> Cc: 46342@debbugs.gnu.org
> Date: Tue, 09 Feb 2021 07:17:29 -0800
>
>
> [1:text/plain Hide]
>
> Eli,
>
> Apologies for my previous rambling reply. Your time is supremely
> valuable, and I should've been more mindful of that. I'm hoping you'll
> allow me this mulligan (ahem):
>
> > That depends on what the other end expects. Does it expect latin-1 in
> > this case?
>
> Yes.
>
> > Does emitting the single byte \330 produce the correct result in this
> > case?
>
> Yes.
>
> > Then by all means please use
> >
> > (encode-coding-string address 'latin-1)
>
> I have updated my changes to reflect this.
>
> > And those [tor/ssh] expect Latin-1 encoding in this case?
>
> Yes.
>
> When you've got a sec, please instruct me on how best to proceed (even
> if that means buggering off 'til I've learned more about Emacs!). :)
(I'd really prefer that someone who knows more than I do about SOCKS
review this.)
If I must do that, I have a question: what kind of string can this
ADDRESS be? My reading of RFC 1928 is that it normally is an IP
address, in which case encoding is not relevant, as it's an ASCII
string. But it can also be a domain, right? If so, what form can
this domain take? If the domain has non-ASCII characters, shouldn't
it be hex-encoded, or run through IDNA? I mean, are non-ASCII
characters in that place at all allowed?
next prev parent reply other threads:[~2021-02-09 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 11:46 bug#46342: 28.0.50; socks-send-command munges IP address bytes to UTF-8 J.P.
2021-02-06 12:26 ` Eli Zaretskii
2021-02-06 14:19 ` J.P.
2021-02-06 15:15 ` Eli Zaretskii
2021-02-07 14:22 ` J.P.
2021-02-09 15:17 ` J.P.
2021-02-09 16:14 ` Eli Zaretskii [this message]
2021-02-10 13:16 ` J.P.
2021-02-10 16:04 ` Eli Zaretskii
2021-02-11 14:58 ` J.P.
2021-02-11 15:28 ` Eli Zaretskii
2021-02-12 14:30 ` J.P.
2021-02-12 15:04 ` Eli Zaretskii
2021-02-13 15:43 ` J.P.
2021-02-17 14:59 ` J.P.
2021-02-20 9:33 ` Eli Zaretskii
2021-02-20 10:13 ` J.P.
2021-02-20 11:08 ` Eli Zaretskii
2021-02-20 15:08 ` J.P.
2021-02-20 15:19 ` Eli Zaretskii
2021-02-20 10:41 ` J.P.
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rdpkyl6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46342@debbugs.gnu.org \
--cc=jp@neverwas.me \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).