It doesn't appear to be documented, but from my testing it seems that any flags 
(including -k <key> and -K <key>) must be _before_ the commands ('a', 
'checksig', etc.)

e.g.
vpk -k pubkey checksig my.vpk <-- good
vpk checksig -k pubkey my.vpk <-- bad
vpk checksig my.vpk -k pubkey <-- bad

On 22/03/2013, at 10:17 AM, Fletcher Dunn <[email protected]> wrote:

> Is there a particular question you have that is not answered by the command 
> usage text?
> 
> CREATE VPK / ADD FILES:
>  vpk <dirname>
>         Creates a pack file named <dirname>.vpk located
>         in the parent of the specified directory.
>  vpk a <vpkfile> <filename1> <filename2> ...
>         Add file(s).
>  vpk a <vpkfile> @<filename>
>         Add files listed in a response file.
>  vpk k <vpkfile> <keyvalues_filename>
>         Add files listed in a keyvalues control file.
> 
> EXTRACT FILES:
>  vpk x <vpkfile> <filename1> <filename2> ...
>         Extract file(s).
> 
> DISPLAY VPK INFO:
>  vpk l <vpkfile>
>         List contents of VPK.
>  vpk L <vpkfile>
>         List contents (detailed) of VPK.
>  vpk dumpsig <vpkfile>
>         Display signature information of VPK file
> 
> VPK INTEGRITY / SECURITY:
>  vpk checksig <vpkfile>
>            Verify signature of specified VPK file.
>            Requires -k to specify key file to use.
> 
> MISC:
>  vpk generate_keypair <keybasename>
>            Generate public/private key file.  Output files
>            will be named <keybasemame>.publickey.vdf
>            and <keybasemame>.privatekey.vdf
>            Remember: your private key should be kept private.
> 
> 
> Options:
>  -v     Verbose.
>  -M     Produce a multi-chunk pack file
>  -P     Use SteamPipe-friendly incremental build algorithm.
>         Use with 'k' command.
>         For optimal incremental build performance, the control file used
>         for the previous build should exist and be named the same as the
>         input control file, with '.bak' appended, and each file entry
>         should have an 'md5' value.  The 'md5' field need not be the
>         actual MD5 of the file contents, it is just a unique identifier
>         that will be compared to determine if the file contents has changed
>         between builds.
>         This option implies -M
>  -c <size>
>         Use specified chunk size (in MB).  Default is 200.
>  -a <align>
>         Align files within chunk on n-byte boundary.  Default is 1.
>  -K <private keyfile>
>         With commands 'a' or 'k': Sign VPK with specified private key.
>  -k <public keyfile>
>         With commands 'a' or 'k': Public key that will be distributed
>              and used by third parties to verify signatures.
>         With command 'checksig': Check signature using specified key file.
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of GREFFIER 
> Jonathan
> Sent: Thursday, March 21, 2013 4:12 PM
> To: [email protected]
> Subject: Re: [hlds_linux] How to use VPK Tool ?
> 
> Person to explain to me how to package a file "vpk" and signed with a public 
> key? it's been five days since I'm looking person can answer me ! 
> it's unbelievable...
> 
> 
> 
> 
> Le 21/03/2013 04:18, GREFFIER Jonathan a écrit :
>> Hello,
>> 
>> Could someone explain how to add the public key signature on file 
>> ".vpk" with the tool VPK Tool (Windows) please ?
> 
> 
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
> 
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives, please 
> visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to