Skip to content

Handle ssh key import better #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 24, 2016
Merged

Conversation

stroucki
Copy link
Contributor

(copied from original)
ssh_key: when user submitted keys had a newline at the end, strings.Split
would have created a slice with an empty last element, and the key type
check would be incorrect. Perhaps a better way is to look for 'ssh-rsa' or
'ssh-dsa' at the beginning of the string, but this is simple.

Michael Stroucken added 2 commits October 17, 2016 17:05
ssh_key: when user submitted keys had a newline at the end, strings.Split
would have created a slice with an empty last element, and the key type
check would be incorrect. Perhaps a better way is to look for 'ssh-rsa' or
'ssh-dsa' at the beginning of the string, but this is simple.
@codecov-io
Copy link

Current coverage is 3.03% (diff: 0.00%)

Merging #224 into master will decrease coverage by <.01%

@@            master      #224   diff @@
========================================
  Files           33        33          
  Lines         8106      8107     +1   
  Methods          0         0          
  Messages         0         0          
  Branches         0         0          
========================================
  Hits           246       246          
- Misses        7840      7841     +1   
  Partials        20        20          

Powered by Codecov. Last update cb16028...757fb4d

@tboerger tboerger added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Nov 23, 2016
@bkcsoft
Copy link
Member

bkcsoft commented Nov 23, 2016

LGTM

@tboerger tboerger added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Nov 23, 2016
@bkcsoft bkcsoft added this to the 1.0.0 milestone Nov 23, 2016
@thibaultmeyer
Copy link
Contributor

LGTM

@tboerger tboerger added the lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. label Nov 23, 2016
@lunny lunny merged commit 3a3782b into go-gitea:master Nov 24, 2016
@tboerger tboerger added type/enhancement An improvement of existing functionality and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Nov 24, 2016
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants