forgejo/discussions
49
43

Federation Threat Analysis #438

Open
opened 2026年01月22日 09:15:36 +01:00 by jerger · 0 comments
Member
Copy link

Intended Audience: Forgejo Devs and Devs interested in Security.

On Fr. 23.1. 17:00 - 18:30 CET

at https://jitsi.prod.meissa.de/forgejo

We analyze whether there are new threats introduced by

Milestone 2: Federated Search
https://codeberg.org/forgejo-contrib/federation/milestone/31355

For threat modeling we will try out the forgejo-threats tool

New connections and data-assets will be described here:
repo.prod.meissa.de/meissa/forgejo-threats@c5a5e28425/forgejo-definition.yaml (L215)

If we find new ways to attack, we will describe the attack here:
https://repo.prod.meissa.de/meissa/forgejo-threats/src/branch/main/forgejo-attacks.yaml

Meeting Minutes will be published here:
https://codeberg.org/forgejo-contrib/federation/src/branch/main/meeting-minutes

Intended Audience: Forgejo Devs and Devs interested in Security. On Fr. 23.1. 17:00 - 18:30 CET at https://jitsi.prod.meissa.de/forgejo We analyze whether there are new threats introduced by Milestone 2: Federated Search https://codeberg.org/forgejo-contrib/federation/milestone/31355 For threat modeling we will try out the [forgejo-threats tool](https://repo.prod.meissa.de/meissa/forgejo-threats) New connections and data-assets will be described here: https://repo.prod.meissa.de/meissa/forgejo-threats/src/commit/c5a5e28425d902bb338d824620106145ae33923a/forgejo-definition.yaml#L215 If we find new ways to attack, we will describe the attack here: https://repo.prod.meissa.de/meissa/forgejo-threats/src/branch/main/forgejo-attacks.yaml Meeting Minutes will be published here: https://codeberg.org/forgejo-contrib/federation/src/branch/main/meeting-minutes
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#438
Reference in a new issue
forgejo/discussions
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?