This is Andrey Anastasov's Typepad Profile.
Join Typepad and start following Andrey Anastasov's activity
Join Now!
Already a member? Sign In
Andrey Anastasov
Recent Activity
The credential store is encrypted with .Net's ProtectedData.Protect() function which delegates to Windows' CryptProtectData(). It is considered a secure way to protect data and - to my knowledge - is the method employed by the built-in Windows file encryption (EFS). To decrypt the data, an attacker must have enough information as to log in as the user who encrypted the data. In other words, even if someone steals the harddisk, the data is secure as long as the user password is unavailable to the attacker. An administrator cannot read the data by forcing password reset.
1 reply
Hi Luc, We'd like to keep things as close to the example you're giving as possible. The V1/V2/... part of the name does not indicate intent to make frequent changes. The namespace is meant to change rarely - its purpose is to accommodate breaking changes only when they are inevitable and to do so in a non-disruptive way. We plan for transition period in which both versions are supported. As you suggest, it is possible to keep a single type and rely on PowerShell's type adaptation system to do the job. The downside of this approach is that it leaves us no options for providing backward compatibility to .Net applications which reference PowerCLI types.
1 reply
The "V1" is a sign of a versioning system we plan to implement. When we face a need to make a breaking change in the objects, we plan to mark the new version as V2. The important part - for some period of time we plan to keep the objects support both V1 and V2 interfaces so there's enough time for scripts to migrate to V2. Then in some release V1 would disappear. We're starting at version 1 because we expect that breaking changes will be very rare and the object version doesn't need to change with each PowerCLI release.
1 reply
The driver confirmation window proved very hard to locate indeed. The reason is its odd placement in the window hierarchy - its top level parent is hidden. Jaykul (WASP's author) helped me with locating it. My guess was that I should use Select-Window which is probably what you tried. This works with the vast majority of windows but not with this one. Last thing I know, Jaykul was considering enhancement to Select-Window so it can cover this case. I wouldn't be surprised if it works in WASP's latest version.
1 reply
@LucD, Any day now :) I've been tied on new features lately but it really is about time I wrote the second part. Let's not call it a promise but I plan to post it tomorrow.
1 reply