openssh bugs - Apr 2020 - [Bug 3149] New: Fix typo in readconf error message

https://bugzilla.mindrot.org/show_bug.cgi?id=3149

            Bug ID: 3149
           Summary: Fix typo in readconf error message
           Product: Portable OpenSSH
           Version: 8.2p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Keywords: patch
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: jjelen at redhat.com

Created attachment 3383
  --> https://bugzilla.mindrot.org/attachment.cgi?id=3383&action=edit
proposed patch

While reading through the code, I noticed this copy&paste error. Patch
attached

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3149

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |dtucker at dtucker.net
         Resolution|---                         |FIXED
             Blocks|                            |3117

--- Comment #1 from Darren Tucker <dtucker at dtucker.net> ---
Patch applied, thanks.


Referenced Bugs:

https://bugzilla.mindrot.org/show_bug.cgi?id=3117
[Bug 3117] Tracking bug for 8.3 release
-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3149

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #2 from Damien Miller <djm at mindrot.org> ---
closing resolved bugs as of 8.6p1 release

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3149

Ahmed Sayeed <ahmedsayeed1982 at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahmedsayeed1982 at yahoo.com

--- Comment #3 from Ahmed Sayeed <ahmedsayeed1982 at yahoo.com> ---
"The strncat() function shall append not more than n bytes (a null byte
and bytes that follow it are not appended) from the array pointed to by
s2 to the end of the string pointed to by s1."
http://www-look-4.com/category/technology/

The wording imply that the third "n" argument is an additional
boundary
limit, not the destination buffer capacity (ie. the destination buffer
is not implicitly SIZE_MAX),
https://komiya-dental.com/health/healthy-foods/ and both source and
destination do not overlap (overlapping depends on the source and
destination layout, not on the "n" value)
http://www.iu-bloomington.com/computers/invisible-with-vpn/

However, it seems that the optimized strncat version of the GLIBC
behaves incorrectly, when using this value.
https://waytowhatsnext.com/sports/navona/
"The strncat() function shall append not more than n bytes (a null byte
and bytes that follow it are not appended) from the array pointed to by
s2 to the end of the string pointed to by s1."
https://www.webb-dev.co.uk/sports/sports-and-health/
The wording imply that the third "n" argument is an additional
boundary
limit, not the destination buffer capacity (ie. the destination buffer
is not implicitly SIZE_MAX), and both source and destination
http://www.wearelondonmade.com/category/tech/ do not overlap
(overlapping depends on the source and destination layout, not on the
"n" value)

However, it seems that the optimized strncat version of the GLIBC
behaves incorrectly, when using this value.
http://www.jopspeech.com/category/technology/
"The strncat() function shall append not more than n bytes (a null byte
and bytes that follow it are not appended) from the array pointed to by
s2 to the end of the string pointed to by s1."
http://joerg.li/category/technology/
The wording imply that the third "n" argument is an additional
boundary
limit, not the destination buffer capacity (ie. the destination buffer
is not implicitly SIZE_MAX), and both source and destination do not
http://connstr.net/category/technology/ overlap (overlapping depends on
the source and destination layout, not on the "n" value)

However, it seems that the optimized strncat version of the GLIBC
behaves incorrectly, when using this value.
http://embermanchester.uk/category/technology/
"The strncat() function shall append not more than n bytes (a null byte
and bytes that follow it are not appended) from the array pointed to by
s2 to the end of the string pointed to by s1."
 http://www.slipstone.co.uk/category/technology/
The wording imply that the third "n" argument is an additional
boundary
limit, not the destination buffer capacity (ie. the destination buffer
is not implicitly SIZE_MAX), and both source and destination do not
overlap http://www.logoarts.co.uk/category/technology/ (overlapping
depends on the source and destination layout, not on the "n" value)

However, it seems that the optimized strncat version of the GLIBC
behaves incorrectly, when using this value.
http://www.acpirateradio.co.uk/category/technology/
"The strncat() function shall append not more than n bytes (a null byte
and bytes that follow it are not appended) from the array pointed to by
s2 to the end of the string pointed to by s1."
http://www.compilatori.com/category/technology/

The wording imply that the third "n" argument is an additional
boundary
limit, not the destination buffer capacity (ie. the destination buffer
is not implicitly SIZE_MAX), and both source and destination do not
overlap (overlapping depends on the source and destination layout, not
on the "n" value) 

However, it seems that the optimized strncat version of the GLIBC
behaves incorrectly, when using this value.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.