Uniquely ID a machine?
-
This is a strange request -- but I clues on how to uniquely identify a machine. I need this for an online service -- one that needs to be able to control it's troubled users, and attempt to keep them off the system. We'd like something that would survive a hard disk reformat. We have used methods which mark their machine. Marking their registry was quick and easy, but eventually found by the users. We've found that marking they system with a file is somewhat more effective, especially with a well named file. Is there any other way to mark the machine -- could we create a bad sector on the hard drive? Though how would we find it? Is there room in the CMOS for some additional stuff? Any suggestions? Anything we'd do would have to evade the virus software. But, what we'd really like to do, is find a way to identify someone's machine without placing a mark on it. We'd like to be able to piece together a signature based on multiple items, forming a unique id for that machine. * MAC Address: not effective -- dialup users don't have em * BIOS Checksum: may be a good piece of info * Fixed Disc Serial #: may be a good piece of info * ???? Thanks -p
-
This is a strange request -- but I clues on how to uniquely identify a machine. I need this for an online service -- one that needs to be able to control it's troubled users, and attempt to keep them off the system. We'd like something that would survive a hard disk reformat. We have used methods which mark their machine. Marking their registry was quick and easy, but eventually found by the users. We've found that marking they system with a file is somewhat more effective, especially with a well named file. Is there any other way to mark the machine -- could we create a bad sector on the hard drive? Though how would we find it? Is there room in the CMOS for some additional stuff? Any suggestions? Anything we'd do would have to evade the virus software. But, what we'd really like to do, is find a way to identify someone's machine without placing a mark on it. We'd like to be able to piece together a signature based on multiple items, forming a unique id for that machine. * MAC Address: not effective -- dialup users don't have em * BIOS Checksum: may be a good piece of info * Fixed Disc Serial #: may be a good piece of info * ???? Thanks -p
You can use GetVolumeInformation() to find disc serial #. That's the best I can think of. :confused: I vote pro drink :beer:
-
This is a strange request -- but I clues on how to uniquely identify a machine. I need this for an online service -- one that needs to be able to control it's troubled users, and attempt to keep them off the system. We'd like something that would survive a hard disk reformat. We have used methods which mark their machine. Marking their registry was quick and easy, but eventually found by the users. We've found that marking they system with a file is somewhat more effective, especially with a well named file. Is there any other way to mark the machine -- could we create a bad sector on the hard drive? Though how would we find it? Is there room in the CMOS for some additional stuff? Any suggestions? Anything we'd do would have to evade the virus software. But, what we'd really like to do, is find a way to identify someone's machine without placing a mark on it. We'd like to be able to piece together a signature based on multiple items, forming a unique id for that machine. * MAC Address: not effective -- dialup users don't have em * BIOS Checksum: may be a good piece of info * Fixed Disc Serial #: may be a good piece of info * ???? Thanks -p
Peter Weyzen wrote: could we create a bad sector on the hard drive? That would work, as long as you don't mind getting sued by your users for willful destruction of their property. --Mike-- http://home.inreach.com/mdunn/ Help! Help! I'm being repressed!! :love: your :bob: with :vegemite: and :beer: Sonork - 100.10414 AcidHelm
-
Peter Weyzen wrote: could we create a bad sector on the hard drive? That would work, as long as you don't mind getting sued by your users for willful destruction of their property. --Mike-- http://home.inreach.com/mdunn/ Help! Help! I'm being repressed!! :love: your :bob: with :vegemite: and :beer: Sonork - 100.10414 AcidHelm
well, thanks for the legal advice... seems like no one has any information on this topic...
-
This is a strange request -- but I clues on how to uniquely identify a machine. I need this for an online service -- one that needs to be able to control it's troubled users, and attempt to keep them off the system. We'd like something that would survive a hard disk reformat. We have used methods which mark their machine. Marking their registry was quick and easy, but eventually found by the users. We've found that marking they system with a file is somewhat more effective, especially with a well named file. Is there any other way to mark the machine -- could we create a bad sector on the hard drive? Though how would we find it? Is there room in the CMOS for some additional stuff? Any suggestions? Anything we'd do would have to evade the virus software. But, what we'd really like to do, is find a way to identify someone's machine without placing a mark on it. We'd like to be able to piece together a signature based on multiple items, forming a unique id for that machine. * MAC Address: not effective -- dialup users don't have em * BIOS Checksum: may be a good piece of info * Fixed Disc Serial #: may be a good piece of info * ???? Thanks -p
That's a very tough one. All of the options mentioned require binary executables to run which probably rules out cross-platform compatability (PCs and Macs.) Personally, I have my security level set very high and I do not allow ANY Active-X crap or scripts to run without permission which I nearly always deny. Is user login not an option ?
-
That's a very tough one. All of the options mentioned require binary executables to run which probably rules out cross-platform compatability (PCs and Macs.) Personally, I have my security level set very high and I do not allow ANY Active-X crap or scripts to run without permission which I nearly always deny. Is user login not an option ?
well, to add some more information here. In order to access our system, one must install our client software. So "permissions" on a client machine would not be a problem. just doing a login is not sufficient. We would like to bar "problem users" from getting on to our system. Some of them will purchase a new membership after we shutdown a problem account. If we could identify their machine uniquely, we could stop them from accessing our system. We could not stop them from using another machine, but blocking a single machine is an effective deterrant. We've used various "cookie" type mechanisms -- placing markers on their machine either in the file system or in the registry. All of these tactics are detectable, and may be circumvented (and have been). We're just trying to prevent a very small number of extremely annoying people from using our system. There are a lot of "obvious" ID's that people suggest, but don't really do much: - IP - doesn't work, cannot control dynamic IP users - MAC address - dialup users don't have a unique one With the new XP, Microsoft has started to employ the same mechanisms we seek... But they don't share stuff like that. Thanks