From owner-freebsd-hackers Tue Sep 16 00:52:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02186 for hackers-outgoing; Tue, 16 Sep 1997 00:52:28 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02152 for ; Tue, 16 Sep 1997 00:52:22 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id RAA07394; Tue, 16 Sep 1997 17:51:54 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id RAA17699; Tue, 16 Sep 1997 17:50:43 +1000 (EST) Message-Id: <199709160750.RAA17699@ogre.dtir.qld.gov.au> To: Simon Shapiro cc: freebsd-hackers@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: Fast Encryption (in kernel) seeked References: In-Reply-To: from Simon Shapiro at "Tue, 16 Sep 1997 04:57:46 +0000" Date: Tue, 16 Sep 1997 17:50:42 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, 16th September 1997, Simon Shapiro wrote: >I have a specific integer (actually a pointer to a structure) which, for >performance reasons, I want exported to userspace. What happens with this >pointer is that sometimes later it comes back to the kernel. > >I want a QUICK was to encrypt it so that a melicious user cannot send a bad >address into the kernel. >If this sounds like harebrain idea, it probably is :-) No need for me to go on about it, since you've admitted it. ;-) I'm sure that encryption would just be hand waving and hoping. I don't think it would add any value. Picking a real random number (from the /dev/random module) and using that as an index might work. But really I think you should give us more details to work on. More than likely you don't have to do what you want to do. Give us the wider picture, and a clean answer is likely to result. Stephen.