github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Bank-sync operations are not e2e encrypted #1104

New Issue
Closed
opened 2026-02-28 19:32:03 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:32:03 -06:00
Owner
Copy Link

Originally created by @MatissJanis on GitHub (May 16, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

E2E encryption currently works only for the main budget file (and its sync with the server). It does not, however, work for the bank-sync operation.

We should introduce e2e encryption to the bank-sync operation too (if it is enabled).

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @MatissJanis on GitHub (May 16, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [ ] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? E2E encryption currently works only for the main budget file (and its sync with the server). It does not, however, work for the bank-sync operation. We should introduce e2e encryption to the bank-sync operation too (if it is enabled). ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bank syncbug labels 2026-02-28 19:32:03 -06:00
GiteaMirror commented 2026-02-28 19:32:04 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 19, 2025):

I don't know what I was thinking when I created this issue. E2E encryption would not work for bank sync operations as we are not PUSHING information to the server, but instead are PULLING. And the server has no knowledge about the encryption keys, so it is not able to encrypt the bank-sync transactions.

@MatissJanis commented on GitHub (Mar 19, 2025): I don't know what I was thinking when I created this issue. E2E encryption would not work for bank sync operations as we are not PUSHING information to the server, but instead are PULLING. And the server has no knowledge about the encryption keys, so it is not able to encrypt the bank-sync transactions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bank sync bug
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/actual#1104
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?