gpg encrypted communication #2026

New Issue

GiteaMirror · 2025-11-02T04:21:36-06:00

GiteaMirror commented

2025-11-02 04:21:36 -06:00

Originally created by @volker-raschek on GitHub (Jul 8, 2018).

Hello,
I have a suggestion for improvement. Since gitea stores the e-mail address and optionally the public gpg key, it should be possible for gitea to send encrypted e-mails.

I thought that if the user has stored his public gpg key, he will find an option in his settings to encrypt the mail communication.

To do this, gitea sends him an encrypted mail with an activation link to ensure that the user is able to read encrypted mails.

If the user opens the activation link, the communication is automatically gpg encrypted.

Originally created by @volker-raschek on GitHub (Jul 8, 2018). Hello, I have a suggestion for improvement. Since gitea stores the e-mail address and optionally the public gpg key, it should be possible for gitea to send encrypted e-mails. I thought that if the user has stored his public gpg key, he will find an option in his settings to encrypt the mail communication. To do this, gitea sends him an encrypted mail with an activation link to ensure that the user is able to read encrypted mails. If the user opens the activation link, the communication is automatically gpg encrypted.

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 04:21:36 -06:00

GiteaMirror commented

2025-11-02 04:21:37 -06:00

@stale[bot] commented on GitHub (Jan 16, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 16, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:21:37 -06:00

@zeripath commented on GitHub (Jan 16, 2019):

This is quite a cool idea actually. I think we should keep this issue around.

@zeripath commented on GitHub (Jan 16, 2019): This is quite a cool idea actually. I think we should keep this issue around.

GiteaMirror commented

2025-11-02 04:21:37 -06:00

@zeripath commented on GitHub (Jan 24, 2020):

I have a number of queries about this. Where can I look to find how we are supposed to do this?

For example:

Are we supposed to encrypt the headers or the subject?
Do we encrypt the plain and the html together? How does that work?

@zeripath commented on GitHub (Jan 24, 2020): I have a number of queries about this. Where can I look to find how we are supposed to do this? For example: * Are we supposed to encrypt the headers or the subject? * Do we encrypt the plain and the html together? How does that work?

GiteaMirror commented

2025-11-02 04:21:37 -06:00

@volker-raschek commented on GitHub (Feb 11, 2025):

Hi @zeripath, any news regarding my feature request?

@volker-raschek commented on GitHub (Feb 11, 2025): Hi @zeripath, any news regarding my feature request?

GiteaMirror referenced this issue

2025-11-02 12:04:15 -06:00

[PR #2026] [CLOSED] Show callstack backstraces for 'Internal Server Error 500 #16186

Sign in to join this conversation.