bugGNU Screen - Bugs: bug #63096, IPV6 utmp entry shorthand address...

 
 

bug #63096: IPV6 utmp entry shorthand address should include least significant bytes

Submitter:  None
Submitted:  Fri 23 Sep 2022 02:40:53 PM UTC
 
Category:  Feature Request Severity:  3 - Normal
Priority:  * 5 - Normal Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  4.8.0
Fixed Release:  None Planned Release:  None
Work Required:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Fri 23 Sep 2022 02:40:53 PM UTC, original submission:  

When gnu-screen writes into utmp the IPv6 address of connected ptys, it looks like:

user     pts/0        Sep 23 07:18 (2602:512a:b522:551e:3f90:1da6:437c:3a49)
user     pts/1        Aug 21 08:42 (2602:S.0)
user     pts/2        Aug 21 08:42 (2602:S.1)
user     pts/4        Sep 16 17:02 (2602:S.2)

when there's IPv6 addresses that can't be reverse resolved.  The prefix 2602:: could mean a LOT of different hosts.  The suggestion is to use the least significant digits of the IPV6 address (...3a49:S.0), or perhaps (2602...3a49:S.x) in the utmp entries.

Note that the shorthand was probably meant for chopping up fully resolved names and not unresolvable IPV6 numeric IP addresses.  The current handling, if it effectively were used for IPv4, would show as (127:S.0) for 127.0.0.1 which again is a lot of hosts, and would venture that using even (127...1:S.0) or (...1:S.0) would be more useful to people debugging connections, where one could look in the kernel IP connection tables to find the remote address.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

 

 

 

No changes have been made to this item

Back to the top


Powered by Savane 3.9