This content has been marked as final. Show 4 replies
it's as secure as SBAdmin or the client - it uses the same communications layer etc.
so, if you can think of a way of protecting the password or adminauth embedded into the script itself, the risk profile is the same.
Why not write your own web-based recovery code generator using the COM api and ASP for example?
Now you're on to something! I run a ColdFusion server that I can make COM calls with. Would I need the SB client installed on the server, or can I get away with just the EXE and those two supporting DLLs?
You'd need most of a client directory, but you don't need a client active, drivers, or any services - you can dump the graphics/locale directories but otherwise just copy the SafeBoot directory from a client and stick the DLL's in that. Don't forget to register sbadmcom.dll
We used the API to build our own functions for a web page as well. Most of it is for issuing user/machine codes (but we use returned info to deny certain machines/users... like machine-STOLEN or user accounts like "itsupport". We also use it to move/rename machines in the database.