I dont see any reason yet that would convince me to want to be able to un-tokenize a script. All the problems that are being pointed out would still exist if tokenized was not in the picture at all.

If your login scripts accidentally get deleted and there are no tokenized scripts you are still in the same boat arent you? I dont think the purpose for the tokenized scripts are in any way a means of backup.

And I would hope that any scripts or scheduled tasks that suddenly and mysteriously appeared on servers/clients around the same time an angry ex-employee leaves would be removed whether you were able to read them or not.

I would only opt for the de-tokenizing if there was some kind of unique password protection or something like that. The whole point of it for me would be so that other admins/users couldn't get in there and "improve" login scripts that they did not write. None of our scripts are so big that the comporession aspect plays a big role. Its mostly the obfuscation that Im looking forward to. And if anyone simply has to find the correct command line switch to convert it back to clear text then I dont see any point in the obfuscation to begin with.

Just my 2 cents on the subject.