Yes, I totally agree. There is no security advantage to be gained. For our
case, any user (and reviewboard has its own user) on our network has a
password protected rsa key pair so to set up reviewboard required some
hoops to be jumped through. Allowing a password just makes setup simpler :)
Ba
On 2013-05-02 06:36, Tim wrote:
On Wednesday, May 1, 2013 8:35:18 PM UTC+1, Matthew Woehlke wrote:
On 2013-05-01 07:23, Tim wrote:
Review Board won't handle password protected private keys. If
you entered a passphrase when generating the key then I found
ReviewBoard can't handle it.
Well...
Same place it's stores all the other passwords? Admittedly, this is a
feature that imho is missing.
Tim
On Wednesday, May 1, 2013 8:35:18 PM UTC+1, Matthew Woehlke wrote:
>
> On 2013-05-01 07:23, Tim wrote:
> > Review Board won't handle password protected private keys. If you
> entered a
> >
On 2013-05-01 07:23, Tim wrote:
Review Board won't handle password protected private keys. If you entered a
passphrase when generating the key then I found ReviewBoard can't handle it.
Well... yeah. Where would RB store the pass-phrase? :-)
--
Matthew
--
Want to help the Review Board project?
Review Board won't handle password protected private keys. If you entered a
passphrase when generating the key then I found ReviewBoard can't handle it.
BAD:
-BEGIN RSA PRIVATE KEY-
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,85167E3A8D2D8131CEEFC74E556378BC
qg1I0mSPigMqCKLx4jDX/ueLhOm
Hi,
We use Paramiko, an SSH library written in Python, for all SSH key
verification. I've never seen it fail before except when something that was not
a private SSH key was thrown at it (a garbage file or a public key).
Does the file start with "BEGIN RSA PRIVATE KEY-" and end with
"--
Hi,
I'm trying to upload an id_rsa private key to reviewboard to authenticate
with Git repo, but it fails with the error
Uploading SSH key failed: This SSH key is not a valid RSA or DSS key
Permissions on id_rsa were set using chmod 600
Thanks,
M
--
Want to help the Review Board project? Dona