GitLab and SSH keys

最新推荐文章于 2025-10-16 13:00:31 发布
原创 最新推荐文章于 2025-10-16 13:00:31 发布 · 855 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了如何在GitBash中配置用户名和邮箱，生成SSH密钥，并将其添加到GitLab中，实现安全的远程仓库访问。步骤包括检查SSH密钥存在情况，生成新的SSH密钥，复制并粘贴SSH密钥至GitLab账户。

下载安装好gitbash

1.配置用户名和邮箱：

举例：

$ git config --global user.name "zxm 

$ git config --global user.email "zxm@xxx.com"

2.检查是否有ssh key:

cat ~/.ssh/id_rsa.pub

为空说明没有，需要生成

3.生成ssh key:

ssh-keygen -t rsa -C "your.email@example.com" -b 4096

4.复制ssh key：

cat ~/.ssh/id_rsa.pub | clip

5.登陆gitlab,点开Profile Settings--》SSH Keys，把刚才复制的内容粘贴进去。注意是以ssh-rsa开头，以邮箱结尾

 

 

彩蛋：查看git bash中用户名和邮箱：

git config --list

 

17.（开发工具篇Gitlab）如何在Gitlab配置ssh key
地图之家
10-10 1109
17.（开发工具篇Gitlab）如何在Gitlab配置ssh key
GitLab添加SSH key
xiaojinger_123的博客
01-04 8194
SSH 为 Secure Shell 的缩写，SSH 为建立在应用层基础上的安全协议。SSH 是目前较可靠，专为远程登录会话和其他网络服务提供安全性的协议。利用 SSH 协议可以有效防止远程管理过程中的信息泄露问题。ssh-keygen。
Gitlab 生成 SSH Keys
Tina_1202的博客
04-04 1649
本文章基于 Git clone ‘your Project’报错Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.故记录一个解决方案报...
生成GitLab 的SSH 密钥
最新发布
Made In SQL
10-16 631
GitLab是一个基于Git的完整DevOps平台，提供从项目规划到源代码管理、持续集成/部署、监控等全生命周期工具链。它最初由乌克兰开发者Dmitriy Zaporozhets和Valery Sizov于2011年创建，最初名为"GitLab"，是为了解决GitHub当时缺乏的一些企业功能需求。该项目在2013年正式成立公司，现已成为最受欢迎的开源项目之一，每月有超过3000万的注册用户和超过10万个组织使用。
gitlab配置ssh密钥
qq_48691693的博客
10-12 1万+
ssh密钥
gitlab配置ssh key
tangsiqi130的博客
02-18 9571
gitlab配置ssh key
centos7 jenkins配合gitlab使用SSH免密登构建项目
weixin_40009737的博客
03-19 996
前面的安装步骤参考https://blog.youkuaiyun.com/weixin_40009737/article/details/114867449 第一台搭建gitable服务器 1.获取token和获取令牌（webhook配置）* 参考https://blog.youkuaiyun.com/weixin_40009737/article/details/114880726 第二台搭建jenkins服务器** 一、.获取私钥 在gitlab里面添加了ssh key之后，以后本地pull/push就不需要登录了 （1.）获
自建 GitLab 服务 SSH 连接出现 Permission denied 问题
一个码农的回音岛
01-29 1567
自建 GitLab 服务 SSH 连接出现 Permission denied (publickey,gssapi-keyex,gssapi-with-mic) 问题
GitLab and SSH keys Git is a distributed version control system, which means you can work locally, then share or "push" your changes to a server. In this case, the server is GitLab. GitLab uses the SSH protocol to securely communicate with Git. When you use SSH keys to authenticate to the GitLab remote server, you don't need to supply your username and password each time. Prerequisites To use SSH to communicate with GitLab, you need: The OpenSSH client, which comes pre-installed on GNU/Linux, macOS, and Windows 10. SSH version 6.5 or later. Earlier versions used an MD5 signature, which is not secure. To view the version of SSH installed on your system, run ssh -V. Supported SSH key types To communicate with GitLab, you can use the following SSH key types: ED25519 RSA DSA (Deprecated in GitLab 11.0.) ECDSA (As noted in Practical Cryptography With Go, the security issues related to DSA also apply to ECDSA.) Administrators can restrict which keys are permitted and their minimum lengths. ED25519 SSH keys The book Practical Cryptography With Go suggests that ED25519 keys are more secure and performant than RSA keys. OpenSSH 6.5 introduced ED25519 SSH keys in 2014 and they should be available on most operating systems. RSA SSH keys Available documentation suggests that ED25519 is more secure than RSA. If you use an RSA key, the US National Institute of Science and Technology in Publication 800-57 Part 3 (PDF) recommends a key size of at least 2048 bits. The default key size depends on your version of ssh-keygen. Review the man page for your installed ssh-keygen command for details. See if you have an existing SSH key pair Before you create a key pair, see if a key pair already exists. On Windows, Linux, or macOS, go to your home directory. Go to the .ssh/ subdirectory. If the .ssh/ subdirectory doesn't exist, you are either not in the home directory, or you haven't used ssh before. In the latter case, you need to generate an SSH key pair. See if a file with one of the following formats exists: Algorithm Public key Private key ED25519 (preferred) id_ed25519.pub id_ed25519 RSA (at least 2048-bit key size) id_rsa.pub id_rsa DSA (deprecated) id_dsa.pub id_dsa ECDSA id_ecdsa.pub id_ecdsa Generate an SSH key pair If you do not have an existing SSH key pair, generate a new one. Open a terminal. Type ssh-keygen -t followed by the key type and an optional comment. This comment is included in the .pub file that's created. You may want to use an email address for the comment. For example, for ED25519: ssh-keygen -t ed25519 -C "<comment>" For 2048-bit RSA: ssh-keygen -t rsa -b 2048 -C "<comment>" Press Enter. Output similar to the following is displayed: Generating public/private ed25519 key pair. Enter file in which to save the key (/home/user/.ssh/id_ed25519): Accept the suggested filename and directory, unless you are generating a deploy key or want to save in a specific directory where you store other keys. You can also dedicate the SSH key pair to a specific host. Specify a passphrase: Enter passphrase (empty for no passphrase): Enter same passphrase again: A confirmation is displayed, including information about where your files are stored. A public and private key are generated. Add the public SSH key to your GitLab account and keep the private key secure. Configure SSH to point to a different directory If you did not save your SSH key pair in the default directory, configure your SSH client to point to the directory where the private key is stored. Open a terminal and run this command: eval $(ssh-agent -s) ssh-add <directory to private SSH key> Save these settings in the ~/.ssh/config file. For example: # GitLab.com Host gitlab.com PreferredAuthentications publickey IdentityFile ~/.ssh/gitlab_com_rsa # Private GitLab instance Host gitlab.company.com PreferredAuthentications publickey IdentityFile ~/.ssh/example_com_rsa For more information on these settings, see the man ssh_config page in the SSH configuration manual. Public SSH keys must be unique to GitLab because they bind to your account. Your SSH key is the only identifier you have when you push code with SSH. It must uniquely map to a single user. Update your SSH key passphrase You can update the passphrase for your SSH key. Open a terminal and run this command: ssh-keygen -p -f /path/to/ssh_key At the prompts, type the passphrase and press Enter. Upgrade your RSA key pair to a more secure format If your version of OpenSSH is between 6.5 and 7.8, you can save your private RSA SSH keys in a more secure OpenSSH format. Open a terminal and run this command: ssh-keygen -o -f ~/.ssh/id_rsa Alternatively, you can generate a new RSA key with the more secure encryption format with the following command: ssh-keygen -o -t rsa -b 4096 -C "<comment>" Add an SSH key to your GitLab account To use SSH with GitLab, copy your public key to your GitLab account. Copy the contents of your public key file. You can do this manually or use a script. For example, to copy an ED25519 key to the clipboard: macOS: tr -d '\n' < ~/.ssh/id_ed25519.pub | pbcopy Linux (requires the xclip package): xclip -sel clip < ~/.ssh/id_ed25519.pub Git Bash on Windows: cat ~/.ssh/id_ed25519.pub | clip Replace id_ed25519.pub with your filename. For example, use id_rsa.pub for RSA. Sign in to GitLab. In the top right corner, select your avatar. Select Preferences. From the left sidebar, select SSH Keys. In the Key box, paste the contents of your public key. If you manually copied the key, make sure you copy the entire key, which starts with ssh-ed25519 or ssh-rsa, and may end with a comment. In the Title text box, type a description, like Work Laptop or Home Workstation. Optional. In the Expires at box, select an expiration date. (Introduced in GitLab 12.9.) The expiration date is informational only, and does not prevent you from using the key. However, administrators can view expiration dates and use them for guidance when deleting keys. GitLab checks all SSH keys at 02:00 AM UTC every day. It emails an expiration notice for all SSH keys that expire on the current date. (Introduced in GitLab 13.11.) GitLab checks all SSH keys at 01:00 AM UTC every day. It emails an expiration notice for all SSH keys that are scheduled to expire seven days from now. (Introduced in GitLab 13.11.) Select Add key. 翻译一下
07-04
2. 在左侧菜单中选择 **SSH Keys**。 3. 在文本框中粘贴之前复制的公钥。 4. 输入一个标题来标识该密钥（例如“Personal Laptop”）。 5. 点击 **Add key** 按钮。 完成上述步骤后，GitLab 将识别该密钥，并允许...
gitlab git ssh 配置多个帐户-不同git仓库使用不用的ssh key
满地星辰的博客
05-06 4992
gitlab git ssh 配置多个帐户-不同git仓库使用不用的ssh key 生成 ssh - key manager@mobile:~/.ssh$ ssh-keygen -t rsa -C "yangxx@gmail.com" Generating public/private rsa key pair. Enter file in which to save the key (/h...
GitLab配置SSH Keys
F_hawk189的博客
07-03 1199
转载自：https://www.jianshu.com/p/a8de7dc19a46 准备工作： 安装Git Bash工具 1 是否存在id_rsa.pub文件 进入C:\Users\username.ssh目录，检查是否有id_rsa.pub文件，如果存在跳至第3步。 2 生成id_rsa.pub文件 在bash中输入 ssh-keygen -t rsa -C "yourEmail@e...
GitLab添加SSH Key并配置
qq_23825121的博客
07-25 1616
GitLab添加SSH Key并配置
GitLab配置ssh key
KingOfOnePiece的博客
04-25 1万+
3、打开gitlab,找到Profile Settings-->SSH Keys--->Add SSH Key,并把上一步中复制的内容粘贴到Key所对应的文本框，在Title对应的文本框中给这个sshkey设置一个名字，点击Add key按钮。6、查看~/.ssh/目录下的文件,可以看到增加了gitlab_id-rsa、gitlab_id-rsa.pub和github_id-rsa、github_id-rsa.pub四个文件。2、然后打开~/.ssh/id_rsa.pub文件，复制里面的内容。
GitLab 添加 SSH Key
热门推荐
的米-漠石's Blog
01-07 4万+
1. 按说明生成 Key 文件。 2. 将公钥添加到 GitLab SSH Keys 中。（在用户资料页面） 3. 测试 注：SSH 首次连接服务器时，会有 RSA 密码指纹确认，输入 yes 接受，如下图。   以后连接就不会出现确认提示了。
Git配置SSH Keys
Tang__CT的博客
05-05 1117
Git配置SSH Keys 首次安装使用git，需要先配置用户名称和邮箱 打开Git Bash并输入 git config --global user.name "姓名" git config --global user.email "邮箱地址" 检查是否存在ssh目录及对应的key C盘 => 用户 => .ssh 查看对应的ssh-key 用记事本打开.pub文件，将内容全部复制,注意空格 ssh-rsa xxxxxxxxxxxxxxxxxxxxxxxxxxx 将复制
gitlab 配置ssh keys
xingtianyao的博客
10-23 1391
将输出的内容复制，然后打开GitLab，单击settings->SSH Keys,把复制的内容粘贴到到Key中，点击Add key按钮完成添加。git config --global user.email "yxt@hotmail.cm" 配置gitlab 账号邮箱。git config --global user.name "xt.yao" 配置gitlab账号用户名。如果找不到 SSH Keys 页面，就搜索一下。
GitLab_密钥生成（SSH-key）
m0_65273147的博客
04-23 5018
文件路径（删除所有后缀）
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值