From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 19 15:01:12 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 360FE16A40F for ; Tue, 19 Dec 2006 15:01:12 +0000 (UTC) (envelope-from SRS0=GiARlMAY=F5=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 497AB43CA0 for ; Tue, 19 Dec 2006 15:01:02 +0000 (GMT) (envelope-from SRS0=GiARlMAY=F5=metro.cx=fbsd@sonologic.nl) Received: from [10.0.0.200] (sonodc.xs4all.nl [80.127.39.115]) (authenticated bits=0) by mx1.sonologic.nl (8.13.6/8.13.6) with ESMTP id kBJES7OU067161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Dec 2006 14:28:07 GMT Message-ID: <4587F6F1.1050000@metro.cx> Date: Tue, 19 Dec 2006 15:28:01 +0100 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061109 Mandriva/1.5.0.8-1.1mdv2007.0 (2007.0) Thunderbird/1.5.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 80.127.39.115 is authenticated by a trusted mechanism) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0rc3 (mx1.sonologic.nl [82.94.245.21]); Tue, 19 Dec 2006 14:28:07 +0000 (UTC) Subject: unique hardware identification X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 15:01:12 -0000 Hi All, I was wondering, if something like a unique hardware identification would be possible on FreeBSD. I'd like a machine to authenticate to a server, for which it will need a unique identification. Problem is, it should be generated automatically and not easy to fake / detect without already having root access to the box. I'm thinking of something like combining serial numbers from CPU/disks for example, but there does not seem to be a clear way to obtain these (not all cpu's even have a serial number in there). I am just inquiring if someone on this list has an idea that might help with this problem. Gr, Koen