Key management functions, these do not seem appropriate to automate since they should be part of the project setup:
-d <container>
Delete key container named <container>.
-k <outfile>
Generate a new key pair and write it into <outfile>.
-e <assembly> <outfile>
Extract public key from <assembly> into <outfile>.
-i <infile> <container>
Install key pair from <infile> into a key container named <container>.
-m [y|n]
Enable (y), disable (n) or check (no parameter) whether key containers
are machine specific (rather than user specific).
-o <infile> [<outfile>]
Convert public key in <infile> to text file <outfile> with comma separated
list of decimal byte values.
If <outfile> is omitted, text is copied to clipboard instead.
-p <infile> <outfile>
Extract public key from key pair in <infile> and export to <outfile>.
-pc <container> <outfile>
Extract public key from key pair in <container> and export to <outfile>.
-D <assembly1> <assembly2>
Verify <assembly1> and <assembly2> differ only by signature.
View functions, not much point in automating these either
-t[p] <infile>
Display token for public key in <infile> (together with the public key
itself if -tp is used).
-T[p] <assembly>
Display token for public key of <assembly> (together with the public key
itself if -Tp is used).
-v[f] <assembly>
Verify <assembly> for strong name signature self consistency. If -vf is
specified, force verification even if disabled in the registry.
-Vl
List current settings for strong name verification on this machine.
These modify the local machine assembly verification process, so they also seem inapproprate to support
-Vr <assembly> [<userlist>]
Register <assembly> for verification skipping (with an optional, comma
separated list of usernames for which this will take effect). <assembly>
can be specified as * to indicate all assemblies or *,<public key token> to
indicate that all assemblies with the given public key token. Public key
tokens should be specified as a string of hex digits.
-Vu <assembly>
Unregister <assembly> for verification skipping. The same rules for
<assembly> naming are followed as for -Vr.
-Vx
Remove all verification skipping entries.
Which leaves
-q
Quiet mode. This option must be first on the command line and will suppress
any output other than error messages.
-R <assembly> <infile>
Re-sign signed or partially signed assembly with the key pair in <infile>.
-Rc <assembly> <container>
Re-sign signed or partially signed assembly with the key pair in the key
container named <container>.
Which is what I supported ;-)
-David Waite
Ian MacLean wrote:
David,
I'm probably going to add this pretty much as it. Do you think there is scope for a generalised sn task wrapping the sn.exe tool in addittion or as an extension of this delay-sign task ?
Ian
This is my first stab at a NAnt task, so feedback is welcome. This task re-signs delay-signed objects; I have an open-source project which ships with the public key, but the private key is not shipped so that people can properly set trust levels for the software without fear of third-party security exploits.
-David Waite
------------------------------------------------------------------------
// NAntContrib // Co
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
