otr.private_key format is sometimes improperly padded with leading zeros
Sometimes, the resulting `otr.private_key` file has different 00 leading padding than the original format. It seems to only affect the g and x numbers, but that could just be because of my small sample set. The original format sometimes adds 00 padding to the beginning of some numbers, so its not entirely wrong, just sometimes.
- (g #65ABF36AAF6E1F28F26031DB5A9BFBDB76292F9B9507C94D2F2A57CC... + (g #0065ABF36AAF6E1F28F26031DB5A9BFBDB76292F9B9507C94D2F2A57CC...