Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3437

Closed
Open
Created Mar 28, 2013 by Administrator@rootOwner

Add guide or code to migrate the authorized ssh keys when updating to 5.0

Created by: ghost

When upgrading from 4.2 to 5.0, we met the problem of not able to commit to repository when gitolite is totally removed from git user's directory.

The reason is that the file ~git/.ssh/authorized_keys contains the keys with command of gitolite and it is not updated after migrating to gitlab-shell.

Like this:

gitolite:

command="/home/git/gitolite/src/gitolite-shell SOME-KEY-ID",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty KEY-CONTENT

gitlab-shell:

command="/home/git/gitlab-shell/bin/gitlab-shell SOME-KEY-ID",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty KEY-CONTENT

Assignee
Assign to
Time tracking