Command line mode missing Container Signature options

[Matt Astier]

Hi,

Hoping someone can update the Droid command line options in the future. Here is the issue I am encountering.

Droid gives the option for setting a default signature file (ie; droid –s 104) but does not give the same functionality for the Container Signature files. The only way to currently set Droid to the latest Container is to manually select it in the settings of the Droid GUI version.

In my goal to automate Droid through Powershell/CMD Line, all is working quite well with the exception of this one missing option. Also, in a related issue, any future fix of this problem may need to also address the nomenclature of the Container Signature files. Currently they are using a date in the file naming: container-signature-20220311.xml 

So if the command line option is created, there will also have to be an obvious method for defining the Container Signature version number in the same way that's done for the signature files (ie; -s 104). 

The XML file does list a version number: 

<ContainerSignatureMapping schemaVersion="1.0" signatureVersion="29">

But it isn't reflected in the actual file name, which I think would be much better than using a date, IMO. It would also allow for easier automation.

Anyway, I hope someone gets a chance to work on this at some point. Thanks!

Regards,

Matthew

[Matt Palmer]

Hi,

Code to do this has already been merged into the main codebase, so should be in the next release.   You specify container signatures using the version number that is appended to their file name, with the same command used for binary signatures.  So

droid -s 20211028

would set the container signature version 20211028.

Using the version numbers in the XML is an interesting idea to explore further.  The current situation does have the positive benefit that the binary and container signature version numbers will not collide, so it's easy to distinguish them and set with a single command.

Regards,

Matt.

[Matt Astier]

This is great, Matt. Thanks for adding this option in so quickly. How does the command droid -s now distinguish between Container or Binary signatures? Is it checking the users container signatures folder if the number entered at the command line is of a certain size? Just curious.

Thanks again.

Matthew

[Matt Palmer]

Well, it was added a while ago, but not yet released.

It just matches the signature versions available for both binary and container sigs.  Since container and binary versions have different formats there can't be a collision.

Matt 

--
You received this message because you are subscribed to a topic in the Google Groups "droid-list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/droid-list/4YpH6sbJlIA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to droid-list+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/droid-list/2b5df5ef-b84e-445b-bfb0-9043307ff320n%40googlegroups.com.