![]() | |||||||||||||
Messages in this thread |
> Jones D (ISaCS) wrote: > > > <snip> > > A better way would be to have /proc/nvram address the full > nvram space, > > and have the interpretation in a userspace app. > > > You mean /dev/nvram, don't you? > > Marc Yes, I slipped up there.. I think there's another reason for not decoding the upper bytes though. Some BIOS's encode passwords there, which are notoriously insecure. (Do a websearch for BIOS cracker) If this interface were opened up to show the upper bytes, the userspace app to decode them should only decode the upper bytes if the user has the capabilities. regards, d. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:53 [from the cache] ©2003-2008 | |||||||||||||