DragonFly BSD
DragonFly bugs List (threaded) for 2012-10
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[DragonFlyBSD - Bug #2440] (Rejected) utmp/wtmp/lastlog host field too short


From: Alex Hornung via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 30 Oct 2012 11:21:06 -0700

Issue #2440 has been updated by Alex Hornung.

Status changed from New to Rejected

That's what wtmpx, utmpx and lastlogx are for. changing wtmp, utmp and lastlog host field is a no-go as it is pretty much standard (not sure if actual standard).
----------------------------------------
Bug #2440: utmp/wtmp/lastlog host field too short
http://bugs.dragonflybsd.org/issues/2440

Author: Matthias Rampke
Status: Rejected
Priority: Low
Assignee: 
Category: 
Target version: 


In <include/utmp.h> the host field for utmp, wtmp and lastlog is set to 16 characters. This has the effect that both IPv6 addresses and the resolved hostnames sshd puts in lastlog are being truncated. It surfaces as truncated host names in the SSH "Last login: <time> from <host>" message on interactive logins.

IPv6 addresses are max. 39 characters long, 45 if you allow for IPv4 compatible notation: http://stackoverflow.com/questions/166132/maximum-length-of-the-textual-representation-of-an-ipv6-address but since there may be hostnames in there it should probably be MAXHOSTNAME (cf. <sys/param.h>).

Although changing the wtmp and lastlogin file format is probably not easy to achieve safely :(


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]