forks/forgejo
1
0
Fork 0
Code Releases Activity
Beyond coding. We forge. https://codeberg.org/forgejo/forgejo
17131 commits 1 branch 230 tags 570 MiB
Go 80%
go-html-template 7.8%
Roff 5.2%
JavaScript 3.1%
CSS 2.3%
Other 1.4%
Find a file
Gergely Nagy cad9184a36
[GITEA] Allow changing the email address before activation 
During registration, one may be required to give their email address, to
be verified and activated later. However, if one makes a mistake, a
typo, they may end up with an account that cannot be activated due to
having a wrong email address.

They can still log in, but not change the email address, thus, no way to
activate it without help from an administrator.

To remedy this issue, lets allow changing the email address for logged
in, but not activated users.

This fixes gitea#17785.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit aaaece28e4)
(cherry picked from commit 639dafabec)
(cherry picked from commit d699c12ceb)

[GITEA] Allow changing the email address before activation (squash) cache is always active

This needs to be revisited because the MailResendLimit is not enforced
and turns out to not be tested.

See e7cb8da2a8 * Always enable caches (#28527)

(cherry picked from commit 43ded8ee30)

Rate limit pre-activation email change separately

Changing the email address before any email address is activated should
be subject to a different rate limit than the normal activation email
resending. If there's only one rate limit for both, then if a newly
signed up quickly discovers they gave a wrong email address, they'd have
to wait three minutes to change it.

With the two separate limits, they don't - but they'll have to wait
three minutes before they can change the email address again.

The downside of this setup is that a malicious actor can alternate
between resending and changing the email address (to something like
`user+$idx@domain`, delivered to the same inbox) to effectively halving
the rate limit. I do not think there's a better solution, and this feels
like such a small attack surface that I'd deem it acceptable.

The way the code works after this change is that `ActivatePost` will now
check the `MailChangeLimit_user` key rather than `MailResendLimit_user`,
and if we're within the limit, it will set `MailChangedJustNow_user`. The
`Activate` method - which sends the activation email, whether it is a
normal resend, or one following an email change - will check
`MailChangedJustNow_user`, and if it is set, it will check the rate
limit against `MailChangedLimit_user`, otherwise against
`MailResendLimit_user`, and then will delete the
`MailChangedJustNow_user` key from the cache.

Fixes #2040.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit e35d2af2e5)
(cherry picked from commit 03989418a7)
(cherry picked from commit f50e0dfe5e)
2024-01-15 16:47:16 +00:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] Forgejo Actions e2e tests (squash) generate 2024-01-15 13:26:56 +00:00
.gitea [WORKFLOW] yaml issue templates 2024-01-15 14:48:04 +00:00
assets [GITEA] Use maintained gziphandler 2024-01-15 16:11:58 +00:00
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [CLI] implement forgejo-cli 2024-01-15 13:26:55 +00:00
contrib [GITEA] fix VSCode settings 2024-01-15 16:11:59 +00:00
custom/conf [GITEA] notifies admins on new user registration 2024-01-15 16:11:57 +00:00
docker Dockerfile small refactor (#27757) 2023-10-29 09:44:06 +08:00
docs [GITEA] notifies admins on new user registration 2024-01-15 16:11:57 +00:00
models [GITEA] Allow changing the email address before activation 2024-01-15 16:47:16 +00:00
modules [GITEA] test markdown CleanValue to prevent regression 2024-01-15 16:47:16 +00:00
options [GITEA] Allow changing the email address before activation 2024-01-15 16:47:16 +00:00
public [API] Forgejo API /api/forgejo/v1 2024-01-15 14:48:03 +00:00
releases/images [DOCS] RELEASE-NOTES.md 2024-01-15 14:48:03 +00:00
routers [GITEA] Allow changing the email address before activation 2024-01-15 16:47:16 +00:00
services [GITEA] Add download URL for executable files 2024-01-15 16:11:59 +00:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [GITEA] Allow changing the email address before activation 2024-01-15 16:47:16 +00:00
tests [GITEA] Allow changing the email address before activation 2024-01-15 16:47:16 +00:00
web_src [GITEA] Use vertical tabs on issue filters 2024-01-15 16:11:57 +00:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out [GITEA] Enable mocked HTTP responses for GitLab migration test 2024-01-15 16:11:58 +00:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
.gitattributes [META] Use correct language for .tmpl 2024-01-15 14:48:03 +00:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-01-15 14:48:04 +00:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml Remove go versions from .golangci.yml (#27953) 2023-11-07 22:03:27 +01:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml
.stylelintrc.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) 2023-10-13 15:38:27 +00:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2024-01-15 14:48:04 +00:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-01-15 14:48:03 +00:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2024-01-15 13:26:56 +00:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-01-15 13:26:56 +00:00
go.mod [GITEA] Use existing error functionality 2024-01-15 16:11:58 +00:00
go.sum [GITEA] Use maintained gziphandler 2024-01-15 16:11:58 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-01-15 14:48:03 +00:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2024-01-15 14:48:04 +00:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [SEMVER] 7.0.0+0-gitea-1.22.0 2024-01-15 15:45:14 +00:00
package-lock.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
package.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
poetry.lock Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
poetry.toml Clean up pyproject.toml and package.json, fix poetry options (#25327) 2023-06-18 18:13:08 +00:00
pyproject.toml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
README.md [DOCS] README 2024-01-15 14:48:03 +00:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2024-01-15 14:48:03 +00:00
vitest.config.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2024-01-15 14:48:03 +00:00

README.md

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo – the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.

Learn more

Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.