linux-kernel - RE: [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5E6794FC7B8FCA41A704019BE3C70E8B9422FC49@MX31A.corp.emc.com>
Date:	Fri, 18 Nov 2011 12:50:38 -0500
From:	<peter.staubach@....com>
To:	<john@...va.COM>
CC:	<Trond.Myklebust@...app.com>, <linux-nfs@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS
 errors

The log messages are for the poor admin who has to figure out why nothing is working for the user.

		ps


-----Original Message-----
From: John Hughes [mailto:john@...va.COM] 
Sent: Friday, November 18, 2011 11:52 AM
To: Staubach, Peter
Cc: Trond.Myklebust@...app.com; linux-nfs@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors

On 18/11/11 17:27, peter.staubach@....com wrote:
> Given that the poor user will be sitting, with almost nothing working because of the expired ticket, how does the user figure out what is going on or how does the admin help him?
>
> Some guidance seems like a good thing.  Is there really a problem with these messages being printed to the log?
If you're sat at your console with nothing responding how are you going 
to see the log messages?

The "ticket expired" messages are rate limited.

The "Error: state manager failed on NFSv4 server" messages are not rate 
limited, but if you use my "rpc.gssd -e" hack they'll be written to the 
log every 5 seconds all night long.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/