strange ip addres listed when you run "last -i" command

Bug #15236 reported by Linuxg33k
16
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

- at first a few of us in #ubuntu noticed that if you run "last -i" you get a
list of logins with some really strange ip addresses
- two commonly listed addresses that appear in the list are: 194.135.4.8 and
242.135.4.8
- googling and checking the bug tracker revealed nothing of significance in
terms of similar situations or circumstances
- installing xnest and simulating several logins reveals that each time a user
logs in, either one of the above ip addresses show up, amongst the normal local
user ip of 0.0.0.0
- a few users reported other strange ip's listed when you do "last -i" but those
seem to be generated at login as well.

- to reproduce:

1. login as user
2. install xnest
3. login as many times as you like via xnest, after each login do "last -i" on
command line and see the strange ip address corresponding with each login entry
4. alternatively, you can log out and login in using the main login menu (not
via xnest), and after each time to "last -i" to find strange ip addresses
corresponding to the time stamp for the login

- the fix: on my debian systems all entries correspond to the exact ip address
from which we are logging into that machine, so ideally since this test was done
as a local use on a local machine all ip entries should read 0.0.0.0

Revision history for this message
Matt Zimmerman (mdz) wrote :

It seems like perhaps gdm is not initializing the memory used for that field, or
some such. I don't think there's a security issue here.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still have this issue? It seems to be fixed here

Revision history for this message
Jorge Castro (jorge) wrote :

*** Bug 18831 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

Works fine with the current version, the bug has been fixed since hoary, I'm
closing it. Feel free to reopen if that's still an issue for you with the new
versions.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

This is the output of last -a -i on 6.10 desktop. It's more than just the reboot entry that is getting the bogus IP printed.

reboot system boot Wed Oct 3 06:26 - 22:01 (2+15:34) 236.92.2.0
ken pts/2 Mon Oct 1 15:19 - 06:23 (1+15:04) 153.3.9.0
ken pts/1 Mon Oct 1 15:19 - 06:23 (1+15:04) 91.120.11.0
ken pts/0 Mon Oct 1 15:18 - 06:23 (1+15:04) 154.67.14.0
ken :0 Mon Oct 1 15:18 - 06:24 (1+15:06) 0.0.0.0
reboot system boot Mon Oct 1 15:17 - 06:24 (1+15:06) 0.203.1.0
ken pts/2 Mon Oct 1 09:00 - 13:33 (04:32) 190.162.12.0
ken pts/1 Mon Oct 1 09:00 - 13:33 (04:33) 200.54.10.0
ken pts/0 Mon Oct 1 09:00 - 13:33 (04:33) 216.209.7.0
ken :0 Mon Oct 1 08:34 - 13:33 (04:59) 0.0.0.0
reboot system boot Mon Oct 1 08:34 - 13:33 (04:59) 91.43.2.0

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.