We're writing some XSL to transform an internal testbed format into FFTB. It works fine until we get to passwords, which are obviously encrypted. I wanted to check and see if there's a public "encrypt" API available to make sure it's encrypted in the same way. If not we have a couple of other options, of which our current favorite candidate is documenting it as "For security reasons import and export of passwords between testbed formats is not supported" in the tool's user guide. 
Yes. That's right. For security reasons, we don't publish the encryption keys. But there would be no harm in us adding a mechanism to encrypt a given password. Perhaps we could add a utility (perhaps an option on itestrt) to do this. Sorry for that hassle.
Yeah, either an API or a utility would be handy.. an API would be good embedded stuff, and the utility would be good for things we run remotely as web services which wouldn't be executed as plugins. for example right now our topology converter hooks directly into the Eclipse file menu extensions for Import and Export, we grab the file, post it to our service, and return the desired format (it's two-way for a variety of formats).
Eventually we'll probably re-write some of the core transform logic into pure Java, but for now it's easier this way since we can loadin some of the format-specific libraries on the services host to avoid re-coding the wheel.
And/or a way to say that various fields are just plain old text. It would be interesting to see whether users in labs really need to have the passwords on machines encrypted. Its one thing if the machines are easily accessible, but if they aren't and/or the passwords in them are defaults or all set to standard values an option to keep it in plain text might be interesting.
It would also be interesting to see whether the TBML standard can help with this. i.e. allow for providing encrypted values.
