The Evoluent Vertical mouses have three base buttons, are ergonomical and is programmable.
* A simple web frontend for manual things, that simply works in modern browsers
* A complete and easy (no SOAP please, yes I'm looking at you BIG-IP/F5) API and/or cli that can be driven from automation tools, and that provides easily for idempotency.
Ngix or whatever it's called is clearly a bot,
It's called Nginx (http://nginx.net/) and it's a well known HTTP and proxy server.
any program that recieves input and performs a task fits that definition
Isn't that also some kind of definition of every networked software?
> "It will be interesting to see how East Texas judges respond
> to this abuse of process perpetrated against their own residents."
abuse of process? Does such a thing exist in the USA?
The idea of just giving everyone a personal password is just not realistic, when talkin of a support shop with many clients. Having all (e.g.) ten colleagues maintaining a personal password for all of your (e.g.) hundred and twenty clients is a nightmare.
Face it, every IT Support shop has a bunch of customers and a bunch of coworkers, all needing access at one time of another to the administrator password, some root accounts, some router enable passwords or other firewall credentials. It obviously is'nt always as easy as using certificate logins with SSH.
Through serving in different support shops myself, I have seen different approaches, from using a pass like "[customer_name_tag][postalcode]" over noting passwords in a Visio network scheme till storing them in a high encrypted distributed database (which was protected with one unique password).
I've been thinking a lot about a pretty safe way of managing passwords, but couldn't find something good enough, especially when accepting solutions which aren't 100% secure to keep the solution a bit usable as most clients aren't big banks or nuclear power plants, but mostly small businesses.
So my by now obvious question to the IT Support guys within the