Repository navigation
Mysql pads PGP keys with zeros if they are less than 16 characters #177
Description
Activity
It really shouldn't do that. GPG will interpret this very incorrectly, and try to use the key of id
CAFE BABE 0000 0000rather thanxxxx xxxx CAFE BABE. The latter scheme, though 8 digits, is valid, because it's the rightmost 8 digits of the key ID. Even0000 0000 CAFE BABEis wrong, unfortunately, because then it will interpret that as a 16 character ID.MySQL makes me very sad.
This is expected behaviour in MySQL http://dev.mysql.com/doc/refman/5.0/en/binary-varbinary.html
There are a couple of solutions to this.
- Use VARBINARY instead of BINARY because MySQL doesn't pad VARBINARY with 0x00 on insert.
- Detect if there are 8 trailing zero's and automatically strip them
Does SQLite3 and everything else we support (I think mariadb also is supported) use VARBINARY? If so, that sounds like a viable option.
Upon searching sqlite's site for VARBINARY, I get no response.
No results for: VARBINARYUpon searching sqlite's site for BINARY, I get a response.
Search results 1..10 of 70 for: BINARYI only searched for BINARY to make sure that they did have that documentation on their site.
Another option is to just use VARCHAR. I'd rather not do anything right now until we get opinions from people.
I'd say VARCHAR.
I'm going to check exactly how they're stringified real quick. It's possible that this is more easily fixed in Go.
Example: CAFEBABE -> CAFEBABE00000000
nil -> 0000000000000000