1. Software Freedom Conservancy
  2. Kallithea
  3. kallithea
  4. Pull requests

Pull requests

#311 Open
Repository
tonich_sh
Branch
ssh
Repository
conservancy
Branch
default

SSH v8

Bitbucket cannot automatically merge this request.

The commits that make up this pull request have been removed.

Bitbucket cannot automatically merge this request due to conflicts.

Review the conflicts on the Overview tab. You can then either decline the request or merge it manually on your local system using the following commands:

hg update default
hg pull -r ssh https://bitbucket.org/tonich_sh/kallithea
hg merge ssh
hg commit -m 'Merged in tonich_sh/kallithea/ssh (pull request #311)'
Author
  1. tonich_sh
Reviewers
Description

Rebased to tip and

  • ssh: fixed key management.
  • ssh: fixed of ssh related paster commands

Comments (2)

  1. Mads Kiilerich

    Todo list from previous iterations:

    Less code duplication in the ssh handlers - refactor simplegit/simplehg and reuse _check_locking_state and others.
    BaseSSHHandler: why commit?
    Logging / debugging with normal log module ... or just use stderr? Need for logging of ssh commands - perhaps something like the celeryd.log.file config setting.
    Why this .handle() on the handlers?
    We should show both http and ssh clone url (cleaner than https://bitbucket.org/oyarzun/kallithea/commits/af19ab7c4c5cc9807f06dedff9722236e164659f )
    Perhaps better use of forms with validation for adding new keys.
    DB upgrade is fine but should be cleaned up and simplified.
    Tests (at least at high level validate that authorized_keys actually is generated correctly and that the handler works for both hg and git)
    API access?
    Why this 'seen' thing on ssh keys - why not have it as a general feature, also for normal login and for api keys?
    Why no expiration as we have on api keys?
    Server error on push when eol extension enabled.