Issue #10: Create database model and UI for SSH authentication support
| Reported by: | Tim Freund |
| State: | resolved |
| Created on: | 2014-07-16 05:45 |
| Updated on: | 2015-01-24 12:53 |
Description
A new database table, "My Account" screen, and controller methods are required to support future SSH access. The new components will be based off of the existing API key components.
Attachments
Comments
Comment by Tim Freund, on 2014-07-16 05:47
I'm working on an implementation of this, and I should have something functional pushed to my Bitbucket hosted fork within the next couple of days.
Comment by Mads Kiilerich, on 2014-07-16 10:30
Nice. Is it similar to Mercurial's contrib/hg-ssh using native sshd, or is it more like a standalone paramiko based thingie?
Comment by Tim Freund, on 2014-07-16 14:25
This issue will only cover the UI and database model for managing SSH keys, since we need to store keys before we can start accepting SSH connections. I'm sure there will be quite a few changes even with that restriction, and I thought that breaking it up into chunks would make it easier to review.
With that said, I first imagined writing a custom paramiko based thing from scratch, because that sounds like fun. Someone in the IRC channel suggested that we look at the code of mercurial-server and gitosis as starting points. They are already mostly tested, and the licenses are compatible. I'll start looking at those once this issue is complete.
Comment by Christian Oyarzun, on 2014-08-01 22:24
I've modified this branch ssh_server_support for kallithea in my fork. Currently it stores keys, but have not figured out the ssh parts yet.
Comment by Mads Kiilerich, on 2014-09-08 16:51
This is better tracked on PR 42
Comment by zwarmapapa, on 2015-01-24 10:15
How is the development of feature going? And what is PR 42?
Comment by Mads Kiilerich, on 2015-01-24 12:53