You're no longer check if the output of is_valid_ssh_key is None?
Correct. The None result would tell that the user entered newline twice, so there's an empty line, but we already totally ignore those in the code where we write the keys out.
This may end up being quite long, no?
Do we also do that for regular ssh keys?
This is only used for "Regular" (user) ssh keys. We don't use this code for deploy keys, since those are a single key at any time, with no newlines (we reject any deploy keys with newlines).
Yes. But we need to go through them all to make sure we don't add a duped key. I could add a new column to store just this key ID, and just do a query on that if you prefer.
I think that would be faster, especially if we index it
Maybe comment why this one doesn't work?
Could we check the gitolite.conf file produced when there is a pubkey added to the project?
3 new commits added
I'm not seeing where this is being called when we create/add a new key (I'm only seeing called when a key is removed)
rebased
indentation looks odd :)
5 new commits added
btw, there are trailing spaces here :)
1 new commit added
Might need a new line after this one :)
6 new commits added
form.ssh_key.data or '' might be needed
form.ssh_key.data or ''
It's looking good to me :)
Pull-Request has been merged by pingou