[9fans] auth/login: can't change uid: i/o count too small

[9fans] auth/login: can't change uid: i/o count too small

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

Dear List,

I am getting the above message when trying to change to another user
on my system. What does it mean?

Regards,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] auth/login: can't change uid: i/o count too small

[erik quanstrom]

> Dear List,
> 
> I am getting the above message when trying to change to another user
> on my system. What does it mean?
> 
> Regards,
> 
> Christian

does "cpu -u $newuser" work?

this is a little bit of a guess, but the key suspect seems to be

port/devcap.c:229: 			error(Eshort);

i.e. there's no '@' in the Quse message.  not sure how that happens.
what does /sys/log/auth say?

my really wild guess is that you changed the hostowner and didn't
add him to /lib/ndb/auth.

- erik

Re: [9fans] auth/login: can't change uid: i/o count too small

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

* erik quanstrom <quanstro@quanstro.net> [071031 13:18]:
> > Dear List,
> > 
> > I am getting the above message when trying to change to another user
> > on my system. What does it mean?
> > 
> > Regards,
> > 
> > Christian
> 
> does "cpu -u $newuser" work?
> 
Yes using cpu works with any user.

> this is a little bit of a guess, but the key suspect seems to be
> 
> port/devcap.c:229: 			error(Eshort);
> 
> i.e. there's no '@' in the Quse message.  not sure how that happens.
> what does /sys/log/auth say?

Nothing related to this event. I get a suspicious warning every day:
bob Oct 30 15:37:10 keyfs starting warnings: 47274196 471c6237

But I am not sure if this is related...

> 
> my really wild guess is that you changed the hostowner and didn't
> add him to /lib/ndb/auth.
> 
My auth file looks like this:

          hostid=bootes
               uid=!adm uid=*

Thanks,

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] auth/login: can't change uid: i/o count too small

[erik quanstrom]

>> what does /sys/log/auth say?
> 
> Nothing related to this event. I get a suspicious warning every day:
> bob Oct 30 15:37:10 keyfs starting warnings: 47274196 471c6237
> 
> But I am not sure if this is related...
> 
>> 
>> my really wild guess is that you changed the hostowner and didn't
>> add him to /lib/ndb/auth.
>> 
> My auth file looks like this:
> 
>           hostid=bootes
>                uid=!adm uid=*

perhaps auth/login is broken.  it doesn't work on my system
at all.  my system isn't 100% up-to-date.

i never have a need for auth/login, so i've never noticed.

- erik

Re: [9fans] auth/login: can't change uid: i/o count too small

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

* erik quanstrom <quanstro@quanstro.net> [071031 13:43]:

> perhaps auth/login is broken.  it doesn't work on my system
> at all.  my system isn't 100% up-to-date.
> 

I tried again with an up-to-date system. I think it is broken for a
long time.

Maybe also broken: passwd(1). What happens if you use it to change
your hostowner's password?

Do you know what the warning about my keyfs means?

Thanks!

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] auth/login: can't change uid: i/o count too small

[erik quanstrom]

> Maybe also broken: passwd(1). What happens if you use it to change
> your hostowner's password?

you also need to do auth/wrkeys if you are going to change the hostowner's
password.  if you use a ken fs, you will also need to set the password on the
fs.  not sure about fossil.

i haven't found it to be broken.  the last time i fiddled with my passwords
was jul 31.

> Do you know what the warning about my keyfs means?

yes.  those two hex numbers are unix times in seconds printed in hex.
(that's an odd way to print that!) they are the current time and the
last time the warning processes was kicked off.  the warning process
mails users with expiring keys.  read keyfs(4).

- erik

Re: [9fans] auth/login: can't change uid: i/o count too small

[johnny]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

I just tried
auth/login bootes
and got the same message:
auth/login: can't change uid: i/o count too small.
Strange. I haven't had any problems with auth, though.

[-- Attachment #2: Type: message/rfc822, Size: 4240 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 537 bytes --]

* erik quanstrom <quanstro@quanstro.net> [071031 13:43]:

> perhaps auth/login is broken.  it doesn't work on my system
> at all.  my system isn't 100% up-to-date.
> 

I tried again with an up-to-date system. I think it is broken for a
long time.

Maybe also broken: passwd(1). What happens if you use it to change
your hostowner's password?

Do you know what the warning about my keyfs means?

Thanks!

Christian

-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2.1.2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] auth/login: can't change uid: i/o count too small

[Christian Kellermann]

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

* erik quanstrom <quanstro@quanstro.net> [071031 14:02]:
 
> yes.  those two hex numbers are unix times in seconds printed in hex.
> (that's an odd way to print that!) they are the current time and the
> last time the warning processes was kicked off.  the warning process
> mails users with expiring keys.  read keyfs(4).

What about this change:
1058,1059c1058,1059
< 			syslog(0, "auth", "keyfs starting warnings: %lux %lux",
< 				now, lastwarning);
---
> 			syslog(0, "auth", "keyfs starting warnings at %s, last was %s",
> 				ctime(now), ctime(lastwarning));

Maybe this would clear up things? Although when reading the BUGs
section of ctime(2) I am not sure whether this would be a good
idea...
-- 
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

Re: [9fans] auth/login: can't change uid: i/o count too small

[erik quanstrom]

> What about this change:
> 1058,1059c1058,1059
> < 			syslog(0, "auth", "keyfs starting warnings: %lux %lux",
> < 				now, lastwarning);
> ---
> > 			syslog(0, "auth", "keyfs starting warnings at %s, last was %s",
> > 				ctime(now), ctime(lastwarning));
> 

i think a simple

			syslog(0, "auth", keyfs starting warnings: last at %uld\n", lastwarning);

would do.  (syslog will datestamp the entry anyway.)

i'm sure everybody's facinated to note that date(1) will accept the time
in seconds in decimal, hex or octal

	; date -n
	1193852589
	; acid
	8.out:386 plan 9 executable
	/sys/lib/acid/port
	/sys/lib/acid/386
	acid: 1193852589
	0x4728bead
	acid: 0x4728bead\O
	010712137255

	; date 0x4728bead
	Wed Oct 31 13:43:09 EDT 2007
	; date 010712137255
	Wed Oct 31 13:43:09 EDT 2007

- erik

Re: [9fans] auth/login: can't change uid: i/o count too small

[Russ Cox]

> i'm sure everybody's facinated to note that date(1) will accept the time
> in seconds in decimal, hex or octal

most plan 9 programs that take integer arguments
accept all three formats.  because they use atoi,
and on plan 9, atoi does.

russ