| 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
| ||
|
Message-ID: <87mwi2kt2s.fsf@purkki.adurom.net> Date: Sat, 08 Feb 2014 08:38:03 +0200 From: Kalle Valo <kvalo@...rom.com> To: Luca Coelho <luca@...lho.fi> Cc: Larry Finger <Larry.Finger@...inger.net>, Johannes Berg <johannes@...solutions.net>, Calvin Owens <jcalvinowens@...il.com>, "David S. Miller" <davem@...emloft.net>, "John W. Linville" <linville@...driver.com>, linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ieee80211: Print human-readable disassoc/deauth reason codes Luca Coelho <luca@...lho.fi> writes: >> Forum, and there we are lucky if we get dmesg output. When we do and it contains >> a deauthentication reason, I always need to bring up a web page to interpret the >> output. With this change, one step could be skipped. > > But is it worth putting this parsing in the *kernel*? I mean, if anyone > is interested enough in the problem, a simple google query is not that > hard, right? Sure, it's not hard to find it. My and Larry's point is more about convenience and user friendliness. On the other hand I do understand that kernel is getting bloated all the time, for example openwrt is suffering from that. So not really sure what is the best. -- Kalle Valo -- 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/
Powered by blists - more mailing lists