Go to file
zeripath 01c10a951b
Fix ssh deploy and user key constraints (#1357) (#5939)
1. A key can either be an ssh user key or a deploy key. It cannot be both.
2. If a key is a user key - it can only be associated with one user.
3. If a key is a deploy key - it can be used in multiple repositories and the permissions it has on those repositories can be different.
4. If a repository is deleted, its deploy keys must be deleted too.

We currently don't enforce any of this and multiple repositories access with different permissions doesn't work at all. This PR enforces the following constraints:

- [x] You should not be able to add the same user key as another user
- [x] You should not be able to add a ssh user key which is being used as a deploy key
- [x] You should not be able to add a ssh deploy key which is being used as a user key
- [x] If you add an ssh deploy key to another repository you should be able to use it in different modes without losing the ability to use it in the other mode.
- [x] If you delete a repository you must delete all its deploy keys.

Fix #1357
2019-02-03 23:56:53 +00:00
.github Force the PR close time to 60 days (#5770) 2019-01-19 12:21:03 -05:00
assets
cmd Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
contrib Change systemd service file to more correctly match Debian & Centos - Fix #4391 (#5777) 2019-01-19 23:55:39 -05:00
custom/conf Make log mailer for testing (#5893) 2019-02-02 21:06:52 -05:00
docker Disable auto-migrate in docker container (#5730) 2019-01-17 22:31:14 -05:00
docs Make log mailer for testing (#5893) 2019-02-02 21:06:52 -05:00
integrations Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
models Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
modules Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
options Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
public Fix wrapping long code lines in UI (#5927) 2019-02-02 16:58:28 +00:00
routers Fix ssh deploy and user key constraints (#1357) (#5939) 2019-02-03 23:56:53 +00:00
scripts
snap
templates Add single commit API support (#5843) 2019-02-02 22:35:17 -05:00
vendor Add single commit API support (#5843) 2019-02-02 22:35:17 -05:00
.changelog.yml
.drone.yml Add migration test (#5773) 2019-01-28 11:18:52 -05:00
.editorconfig
.gitattributes
.gitignore
.lgtm
.revive.toml
BSDmakefile Add BSDmakefile to prevent errors when `make` is called under FreeBSD (#4446) 2018-07-16 20:45:51 +02:00
CHANGELOG.md 1.7.1 changelog (#5919) 2019-01-31 11:42:22 -05:00
CONTRIBUTING.md
DCO
Dockerfile
Gopkg.lock Add single commit API support (#5843) 2019-02-02 22:35:17 -05:00
Gopkg.toml
LICENSE
MAINTAINERS
Makefile Add migration test (#5773) 2019-01-28 11:18:52 -05:00
README.md
README_ZH.md
main.go Include Go toolchain to --version (#5830) 2019-01-24 10:22:51 -05:00
package-lock.json
package.json

README.md

简体中文

Gitea - Git with a cup of tea

Build Status Join the Discord chat at https://discord.gg/NsatcWJ codecov Go Report Card GoDoc GitHub release Help Contribute to Open Source Become a backer/sponsor of gitea

Purpose

The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service. Using Go, this can be done with an independent binary distribution across all platforms which Go supports, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. Want to try it before doing anything else? Do it with the online demo! This project has been forked from Gogs since 2016.11 but changed a lot.

Building

From the root of the source tree, run:

TAGS="bindata" make generate all

More info: https://docs.gitea.io/en-us/install-from-source/

Using

./gitea web

NOTE: If you're interested in using our APIs, we have experimental support with documentation.

Contributing

Expected workflow is: Fork -> Patch -> Push -> Pull Request

NOTES:

  1. YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
  2. If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!

Further information

For more information and instructions about how to install Gitea, please look at our documentation. If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server, or forum!

Authors

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

FAQ

How do you pronounce Gitea?

Gitea is pronounced /ɡɪti:/ as in "gi-tea" with a hard g.

Why is this not hosted on a Gitea instance?

We're working on it.

License

This project is licensed under the MIT License. See the LICENSE file for the full license text.

Screenshots

Looking for an overview of the interface? Check it out!

Dashboard Repository Commits History
Branches Issues Pull Request View
Releases Activity Wiki
Diff Organization Profile