Re: unique hardware identification

2007-02-07 Thread John Baldwin
On Thursday 01 February 2007 14:40, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Luigi Rizzo <[EMAIL PROTECTED]> writes: > : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: > : > In message: <[EMAIL PROTECTED]> > : > Peter Jeremy <[EMAIL PROTECTE

Re: unique hardware identification

2007-02-02 Thread Oliver Fromme
Peter Jeremy wrote: > Daniel Rudy wrote: > > None of this stuff appears on my system and I'm running 6.1. I can't > > even find dmidump anywhere on the system or in ports either. > > Please elaborate. kenv(8) states that it first appeared in 4.1.1 and > I don't recall seeing any reference

Re: unique hardware identification

2007-02-02 Thread Daniel Rudy
At about the time of 2/1/2007 11:33 PM, Danny Braniss stated the following: >> --ikeVEW9yuYc//A+q >> Content-Type: text/plain; charset=us-ascii >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: >>> None of this

Re: unique hardware identification

2007-02-01 Thread Danny Braniss
> > --ikeVEW9yuYc//A+q > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: > >None of this stuff appears on my system and I'm running 6.1. I can't > >even find dmidump

Re: unique hardware identification

2007-02-01 Thread Peter Jeremy
On Thu, 2007-Feb-01 21:49:43 -0800, Daniel Rudy wrote: >None of this stuff appears on my system and I'm running 6.1. I can't >even find dmidump anywhere on the system or in ports either. Please elaborate. kenv(8) states that it first appeared in 4.1.1 and I don't recall seeing any reference to '

Re: unique hardware identification

2007-02-01 Thread Daniel Rudy
At about the time of 2/1/2007 11:40 AM, M. Warner Losh stated the following: > In message: <[EMAIL PROTECTED]> > Luigi Rizzo <[EMAIL PROTECTED]> writes: > : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: > : > In message: <[EMAIL PROTECTED]> > : > Peter Jere

Re: unique hardware identification

2007-02-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Luigi Rizzo <[EMAIL PROTECTED]> writes: : On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: : > In message: <[EMAIL PROTECTED]> : > Peter Jeremy <[EMAIL PROTECTED]> writes: : > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wro

Re: unique hardware identification

2007-02-01 Thread Luigi Rizzo
On Thu, Feb 01, 2007 at 11:38:51AM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Peter Jeremy <[EMAIL PROTECTED]> writes: > : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: > : >If the machine is a PXE-compliant device [2], it should have a GUID/ > : >UUID [1]

Re: unique hardware identification

2007-02-01 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Peter Jeremy <[EMAIL PROTECTED]> writes: : On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: : >If the machine is a PXE-compliant device [2], it should have a GUID/ : >UUID [1] available. This can be exposed by sysutil/hal [3] via the : >smbios.sy

Re: unique hardware identification

2007-01-28 Thread Peter Jeremy
On Sun, 2007-Jan-28 10:39:36 -0600, Jon Passki wrote: >If the machine is a PXE-compliant device [2], it should have a GUID/ >UUID [1] available. This can be exposed by sysutil/hal [3] via the >smbios.system.uuid field. You can also get it via kenv(8) without needing any ports: # kenv smbios.sy

Re: unique hardware identification

2007-01-28 Thread Jon Passki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 27, 2007, at 23:35 , Daniel Rudy wrote: At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the following: 2006/12/19, Koen Martens <[EMAIL PROTECTED]>: Hi All, I was wondering, if something like a uniq

Re: unique hardware identification

2007-01-27 Thread Daniel Rudy
At about the time of 12/19/2006 7:19 AM, Devon H. O'Dell stated the following: > 2006/12/19, Koen Martens <[EMAIL PROTECTED]>: >> Hi All, >> >> I was wondering, if something like a unique hardware identification >> would be possible on FreeBSD. >> >&

Re: unique hardware identification

2006-12-20 Thread Danny Braniss
> > > 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). > > the simplest thing that comes to my mind is parsing `dmidump` for > serial numbers, h

Re: unique hardware identification

2006-12-19 Thread soralx
> 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). the simplest thing that comes to my mind is parsing `dmidump` for serial numbers, hoping there ar

Re: unique hardware identification

2006-12-19 Thread Bill Moran
In response to "Devon H. O'Dell" <[EMAIL PROTECTED]>: > 2006/12/19, Koen Martens <[EMAIL PROTECTED]>: > > Hi All, > > > > I was wondering, if something like a unique hardware identification > > would be possible on FreeBSD. > > > >

Re: unique hardware identification

2006-12-19 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Koen Martens <[EMAIL PROTECTED]> typed: > 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

Re: unique hardware identification

2006-12-19 Thread Devon H. O'Dell
2006/12/19, Koen Martens <[EMAIL PROTECTED]>: 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 b

unique hardware identification

2006-12-19 Thread Koen Martens
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 al