search for: rfc3629

...nd raw(0) | raw(0) again return raw(0) (rather than logical(0)). * intToUtf8() converts integers corresponding to surrogate code points to NA rather than invalid UTF-8, as well as values larger than the current Unicode maximum of 0x10FFFF. (This aligns with the current RFC3629.) * Fix calling of methods on S4 generics that dispatch on ... when the call contains .... * Following Unicode 'Corrigendum 9', the UTF-8 representations of U+FFFE and U+FFFF are now regarded as valid by utf8ToInt(). * range(c(TRUE, NA), finite = TRUE) and similar...

...nd raw(0) | raw(0) again return raw(0) (rather than logical(0)). * intToUtf8() converts integers corresponding to surrogate code points to NA rather than invalid UTF-8, as well as values larger than the current Unicode maximum of 0x10FFFF. (This aligns with the current RFC3629.) * Fix calling of methods on S4 generics that dispatch on ... when the call contains .... * Following Unicode 'Corrigendum 9', the UTF-8 representations of U+FFFE and U+FFFF are now regarded as valid by utf8ToInt(). * range(c(TRUE, NA), finite = TRUE) and similar...

...(0) (rather > than logical(0)). > > * intToUtf8() converts integers corresponding to surrogate code > points to NA rather than invalid UTF-8, as well as values larger > than the current Unicode maximum of 0x10FFFF. (This aligns with > the current RFC3629.) > > * Fix calling of methods on S4 generics that dispatch on ... when > the call contains .... > > * Following Unicode 'Corrigendum 9', the UTF-8 representations of > U+FFFE and U+FFFF are now regarded as valid by utf8ToInt(). > > *...

...sport-24.txt, chapter 11: ---------------------------------------------------------- 11. Additional Messages Either party may send any of the following messages at any time. 11.1 Disconnection Message byte SSH_MSG_DISCONNECT uint32 reason code string description [RFC3629] string language tag [RFC3066] This message causes immediate termination of the connection. All implementations MUST be able to process this message; they SHOULD be able to send this message. The sender MUST NOT send or receive any data after this message, and the recipie...

...string: disconnected by user 0x63 0x74 0x65 0x64 0x20 0x62 0x79 0x20 0x75 0x73 0x65 0x72 Is this not incomplete? In RFC 4253, section 11.1, the payload for this message is defined to be uint32 reason code string description in ISO-10646 UTF-8 encoding [RFC3629] string language tag [RFC3066] Is it the case that if the sender does not want to use a language tag it can omit the language string altogether, or must one still send an empty string - i.e. a sequence of four bytes all set to zero?

https://bugzilla.mindrot.org/show_bug.cgi?id=2058 Bug ID: 2058 Summary: SSH Banner message displays UTF-8 multibyte char incorrrectly Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5

I can confirm that it doesn't happen on Ubuntu 18.04.1 so Peter is most likely correct; it looks like its Windows specific. On Thu, 7 Feb 2019 at 12:55, peter dalgaard <pdalgd at gmail.com> wrote: > > This doesn't seem to be happening on MacOS, neither in Terminal nor RStudio, (R 3.5.1, R-devel, R-patched). So probably Windows specific. > > -pd > > > On 7 Feb

https://bugzilla.mindrot.org/show_bug.cgi?id=2319 Bug ID: 2319 Summary: [PATCH REVIEW] U2F authentication Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at