11
Quote:
SourceGuardian
SourceGuardian 4.0 for PHP is the ultimate protection solution for your PHP scripts. Main feature: Lock to multiple LAN hardware (MAC) addresses.
Very interesting piece of software. Much cheeper than Zen's! Well Found. For what I understood from the product description, however, is that it allows you to encode/encrypt your script and lock it down to an IP address (ie the server you are running it on). Couldn't find any information about its ability to extract MAC address from any clients connecting to it.
Quote:
IPLoc
IPLoc is a script that locates switch and switchport from IP/Mac-data collected from central routers using SNMP. IPLoc works best with switches who handle RFC 1493 (dot1dTp) and/or RFC 2674 (dot1qFdbTable)
I'll be impressed if this script workes beyond the local switch boundry. ie a webserver somewhere would connect to a switch, behind say a company or private firwall and extract port/mac/ip information. It does look like an interesting script and thanks for pointing it out.
Quote:
Lan-Sentry
This suite of PHP scripts is used for configuring a network to limit access to only certain users. Users that are not authorized will get redirected to a page telling them they can't go anywhere unless they get permission. Only authorized users will be given net access.
Couldn't find more info on Hotscripts and the script home page appears to be down
Quote:
<?php
exec("ipconfig /all", $arr, $retval);
for ($i=0;$i<count($arr);$i++) {
echo $arr[$i].'<br>';
}
?>
I don't think the above will work:
1. "ipconfig /all" is a windows command. What if the PHP and Apache installation are running on Linux? Suppose you can then use ifconfig... but then see 2.
2. As I understand it, PHP is a server side scripting engine. So the above code fragment would execute on the webhosting server and will extract the web server's ip address and mac... and not the client's. I suppose client side scriptting like javascript can be used but I don't know if javascript has access to such o/s information from a web browser.
As alternative solution, wouldn't the usage of cookies be a better idea? When a user registers onto the website a long lasting cookie is dumped on their machine. Then again, there is nothing stopping the user then removing the cookie off their machine...
Still thinking about it...
