GitHub Account Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking Projects The GitHub Flow Advanced Pull Requests GitHub using an HTTPS URL to push over, the Git server will ask you for your username and password for authentication. By default it will prompt you on the terminal for this information so the server can tell if and can use various HTTP authentication mechanisms, meaning it’s often easier on the user than something like SSH, since you can use things like username/password authentication rather than having to

GitHub Account Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking Projects The GitHub Flow Advanced Pull Requests GitHub using an HTTPS URL to push over, the Git server will ask you for your username and password for authentication. By default it will prompt you on the terminal for this information so the server can tell if and can use various HTTP authentication mechanisms, meaning it’s often easier on the user than something like SSH, since you can use things like username/password authentication rather than having to

using an HTTPS URL to push over, the Git server will ask you for your username and password for authentication. By default it will prompt you on the terminal for this information so the server can tell if and can use various HTTP authentication mechanisms, meaning it’s often easier on the user than something like SSH, since you can use things like username/password authentication rather than having to set set up to both serve anonymously like the git:// protocol, and can also be pushed over with authentication and encryption like the SSH protocol. Instead of having to set up different URLs for these things

工单与合并请求模板 自动链接引用 合并消息模板 推送 克隆过滤器 (部分克隆) Code Owners Webhooks 受保护的标签 仓库镜像 密钥管理 Multi-factor Authentication (MFA) 开发 玩转 Gitea API 使用指南 OAuth2 提供者 迁移界面 集成 贡献 后端开发指南 前端开发指南 重构指南 本地化 帮助 常见问题 签名。 数据库证书必须在 X509v3 Extended Key Usage 扩展属性中包含 TLS Web Server Authentication ，而客户端证 书则需要在相应的属性中包含 TLS Web Client Authentication 。 在数据库服务器证书中， Subject Alternative Name 或 Common Name 条目之一必须是数据库实例的完全限定域 。这表示将日志输出到文件，使得 fail2ban 可以定 期扫描日志内容。 当用户的身份验证失败时，日志中会记录此类信息： 1. 2018/04/26 18:15:54 [I] Failed authentication attempt for user from xxx.xxx.xxx.xxx 1. 2020/10/15 16:08:44 [E] invalid credentials from xxx

schacon@mylaptop.local 关于在多种操作系统中生成 SSH 密钥的更深入教程，请参阅 GitHub 的 SSH 密钥指南 https://docs.github.com/cn/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key- and-adding-it-to-the-ssh-agent。 配置服务器 。 你可以在 Account settings 页面的 Security 标签页中找到 Two-factor Authentication 设置。 168 图表 88. Security 标签页中的 2FA 点击“Set up two-factor authentication”按钮，会跳转到设置页面。该页面允许你选择是要在登录时使用手 机 app 生成辅助码（一种“基于时间的一次性密码”），还是要 none [@features] imports = False chunked-push = False matrix2 = False parallel-push = False [authentication] email-case-sensitivity = no 这里我们并不会深入介绍这些选项的含义，但是要注意这是一个 INI 格式的文本文件，就像 Git 的配置。 这个文 件指定了全

schacon@mylaptop.local 关于在多种操作系统中生成 SSH 密钥的更深入教程，请参阅 GitHub 的 SSH 密 钥 指 南 https://docs.github.com/cn/authentication/connecting-to- github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh- agent。 配置服务器 Account settings 页 面 的 Security 标 签 页 中 找 到 Two-factor Authentication 设置。 图表 88. Security 标签页中的 2FA 点击“Set up two-factor authentication”按钮，会跳转到设置页面。该页面 允许你选择是要在登录时使用手机 app 生成辅助码（一种“基于时间的一次性 密码”），还是要 none [@features] imports = False chunked-push = False matrix2 = False parallel-push = False [authentication] email-case-sensitivity = no 这里我们并不会深入介绍这些选项的含义，但是要注意这是一个 INI 格式的文 本文件，就像 Git 的配置。 这个文件指定了全局选项，但它可以被仓库特定的