Article View: borland.public.jbuilder.java.language
Article #15343Re: Host Machine Identification
From: Warren Brown
Date: Fri, 18 Jun 1999 00:00
Date: Fri, 18 Jun 1999 00:00
38 lines
1995 bytes
1995 bytes
You can get the TCP/IP address from the InetAddress.getLocalHost() method. It's not really burned in and secure, but it is accessible and should be unique. You could then use other methods in InetAddress to resolve it to a PC host name in dns perhaps. This all pretty much falls apart if you're running dhcp though, unless you have fixed leases, or use MS-WINS to feed your dhcp the machine names. Warren Paul Schultz <pasfam@ix.netcom.com> wrote in message news:375E92D9.DB059828@ix.netcom.com... > Hi, we're enhancing the security in our client/server application by > trading digital > certificates back and forth between the PC clients and the UNIX server > host. > We are using these certificates to both authenticate who is making the > connection > and which sets of data they are allowed to download. We have everything > pretty > much automated, including creation and installation of new certificates. > The one > thing we have not been able to figure out how to do is how to verify > which PC > the user is connecting from. We tried enumerating through the system > properties, > hoping to see a serial number, a MAC address, or anything elst that > would uniquely > identify which PC was being used without having to manually install > "host ID" > certificates on a PC-by-PC basis. Does anyone have any ideas? > > Thanks, > Paul Schultz > Chicago Public Schools > 773-553-1326 > pschultz@csc.cps.k12.il.us > pasfam@ix.netcom.com >
Technical Details
Message-ID:
<376ac0a4.0@socnm002.dot.state.oh.us>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<375E92D9.DB059828@ix.netcom.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,3ec090c2dd632034 X-Google-Attributes: gidf74b3,public From: "Warren Brown" <wbrown@odot.dot.ohio.gov> Subject: Re: Host Machine Identification Date: 1999/06/18 Message-ID: <376ac0a4.0@socnm002.dot.state.oh.us> X-Deja-AN: 491209483 References: <375E92D9.DB059828@ix.netcom.com> Organization: Another Netscape Collabra Server User X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Newsgroups: borland.public.jbuilder.java.language