From: Lowell H. <lha...@vi...> - 2001-07-16 16:53:17
|
Won't that limit the client base possibilities though? If I were a dialup, dsl, or @home user (all of which are DHCP assigned addresses and you're almost guaranteed not to get the same ip back again) and had to log onto a webpage and enter my ip address for this session, few people would want to run the client that didn't have a static ip (effectively eliminating most of your home userbase). Some cable/dsl providors even time out your ip address after 24 hours so you're constantly being reassigned... Maybe if ranges were allowed (12.34.45.*) or domain names (*.adsl.isp.com) it would be bearable. Perhaps a key or password system would be better. Log onto the website and enter a password, which goes into to the grub.conf. Or a key system where each unique client instance must have a server-assigned key put in the conf file, and tracking is done server-side blocking the client if a key-id connects from more than 2 ip addresses in a 6-hour period... and that key is used to encrypt the session. Lowell |