When starting the signing server, it asks you to enter the gpg, signcode, and mar passphrases, and then verifies that it can sign test files before actually starting the https service. If the mar passphrase isn't entered correctly, the signing server will exit, but the signmar process keeps running in the background at 100% CPU. Presumably it's still trying to read the password. We should make sure that signmar is killed off properly in this case. (brian - is it worthwhile looking into why signmar behaves like this)

It is probably due to the borrowed NSS code that reads input in a loop when the input is wrong. Probably in that case we can simply return an error instead.