github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-15 21:31:24 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[PR #2245] [MERGED] feat(fingerprint): add endpoint to reset olm secret based on fingerprint #28608

New Issue
Closed
opened 2026-06-11 00:17:55 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-11 00:17:55 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/2245
Author: @water-sucks
Created: 1/14/2026
Status: ✅ Merged
Merged: 1/15/2026
Merged by: @oschwartz10612

Base: dev ← Head: add-olm-recovery-endpoint-using-fingerprint

📝 Commits (1)

  • 46fd059 feat(olm): reset/send new olm secret if a matching fingerprint is detected

📊 Changes

3 files changed (+127 additions, -0 deletions)

View changed files

📝 server/routers/external.ts (+6 -0)
📝 server/routers/olm/index.ts (+1 -0)
➕ server/routers/olm/recoverOlmWithFingerprint.ts (+120 -0)

📄 Description

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

This attempts to reset an olm secret if a corresponding secret is found.

How to test?

Re-login with a machine after logging out with a client, AND make sure the olm credentials are deleted client-side.

Any clients that use this endpoint should be able to reuse the same olm with a secret that has been reset (aka not the old secret, this should be removed), and a new device should not pop up in the list.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/2245 **Author:** [@water-sucks](https://github.com/water-sucks) **Created:** 1/14/2026 **Status:** ✅ Merged **Merged:** 1/15/2026 **Merged by:** [@oschwartz10612](https://github.com/oschwartz10612) **Base:** `dev` ← **Head:** `add-olm-recovery-endpoint-using-fingerprint` --- ### 📝 Commits (1) - [`46fd059`](https://github.com/fosrl/pangolin/commit/46fd059d5b2d6aa99a5f8e6121ac90793df315ea) feat(olm): reset/send new olm secret if a matching fingerprint is detected ### 📊 Changes **3 files changed** (+127 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `server/routers/external.ts` (+6 -0) 📝 `server/routers/olm/index.ts` (+1 -0) ➕ `server/routers/olm/recoverOlmWithFingerprint.ts` (+120 -0) </details> ### 📄 Description ## Community Contribution License Agreement By creating this pull request, I grant the project maintainers an unlimited, perpetual license to use, modify, and redistribute these contributions under any terms they choose, including both the AGPLv3 and the Fossorial Commercial license terms. I represent that I have the right to grant this license for all contributed content. ## Description This attempts to reset an olm secret if a corresponding secret is found. ## How to test? Re-login with a machine after logging out with a client, AND make sure the `olm` credentials are deleted client-side. Any clients that use this endpoint should be able to reuse the same `olm` with a secret that has been reset (aka not the old secret, this should be removed), and a new device should not pop up in the list. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-11 00:17:55 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#28608
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?