craftablescience / craftablescience/VPKEdit
Signing packfile via CLI or GUI produces inconsistent output.
Open
@craftablescience is already working on this.
Since Sep 11, 2025.
bug
- Dominant language
- C++
- Stars
- 746
- Forks
- 56
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 2
Description
Describe the Bug
Signing the *_dir.vpk once reports the packfile as not verified.
Signing the *_dir.vpk twice via CLI or GUI makes it valid in the CLI but not in the GUI.
The GUI doesn't report it as signed but you can get both CLI and GUI to report the packfile as signed by signing each partfile of a packfile.
To Reproduce
$ ./vpkeditcli --verify-signature ext_dir.vpk
Pack file does not have a signature.
$ ./vpkeditcli -k pf2.privatekey.vdf ext_dir.vpk
Signed VPK using private key at "pf2.privatekey.vdf".
$ ./vpkeditcli --verify-signature ext_dir.vpk
Pack file signature is invalid!
$ ./vpkeditcli -k pf2.privatekey.vdf ext_dir.vpk
Signed VPK using private key at "pf2.privatekey.vdf".
$ ./vpkeditcli --verify-signature ext_dir.vpk
Pack file signature is valid.
VPKEdit Version
v5.0.0-beta.1
Operating System
Linux
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.