Of course you could just stop anyone loading or using any development tools unless they are authorised to do so....
Making it a sackable offence usually works (I think that's a "pink sheet" for those on the western side of the Pond....) Otherwise set the firewall to only accept connections on the UO port from designated IP addresses. Other techniques posted on the group will work as well - but to list a few: 1. firewall with nominated IP address interconnectivity ONLY 2. Restricted accounts with purged VOCs 3. O.S level permissions (or Tivoli Access Manager) 4. Triggers 5. Account level controls (remote verbs etc) 6. UO application-level authentication (suggest public key and one-time-pad for the serious - stops network sniffing) 7. Restrict access to Windows client PCs - stop anyone from doing anything untoward as they don't have permission to load or use that sort of software. 8. firewall 9. firewall I know I said firewall 3 times but I'll say it again *firewall* - there. Why? Because far too many people pay attention to firewalls - that's why I keep on saying use a firewall - yes really - firewalls are good ideas - yep so are DMZs with firewalls. See - I said firewalls again. BTW: Own up - who never changed their default RedBack administrator ID !!AND!! password. Own up folks - how many defaults are there still out there - we all know the default password I am sure? And yes - I have seen RBOScope access possible from the WWW with the default ID and password. Regards JayJay ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
