>with a zero modulus (which suggests the key wasn't unpacked correctly).
my deliberate mistake (it won't be using rsaencrypt but rsadecrypt) happened to highlight the actual problem, which is that strtosk shouldn't accept a string that looks to me (if not to it) like a public key not a private/secret one, producing something with plenty of zero mpint potential divisors. b00f!
