Password protected backups and Samsung Secure Folder not supported

[aviv926]

Hello and thanks for this project!
I tried this project on my backup, but it doesn't seem to support decrypting samsung secure folder

Also, it doesn't seem to support decrypting a backup encrypted with a user-selected password like smart switch allows you to use.

Can you specify which device you used to test your project?
Also the value of the key you use in lib/smartswitch_core/crypto/common.py

DEFAULT_DUMMY_HEX = "9AB412D3C1F2EF658BFC0CFFCCC344D44C0A"

DEFAULT_PENC_IV = bytes.fromhex("26c7d1d26c142de0a3b82f7e8f90860a")

Where do they come from and is it possible to figure out how to get the correct decryption key for my device?
Are they universal for all Samsung devices?
The only place I found this entry is here
https://github.com/bugscale/samsung-s25-research/blob/43455a9940fdf5171a3e7eb4c6a8674dc87b0c92/1click-rce/exploit/final_clean_custom.py#L95

Regarding Samsung's Secure Folder
I found some things online that might give some direction

• https://pdfcoffee.com/download/how-to-decrypt-pin-based-encrypted-backup-data-of-samsung-smartphones-pdf-free.html?reader=1

• Methods for decrypting the data encrypted by the latest Samsung smartphone backup programs in Windows and macOS

[sachk]

Hi!

Unfortunately I never got around to adding support for password protected backups. I tested it with a Z Fold 5. I'm happy to accept a PR for password protected backup support - It shouldn't be difficult for a modern LLM to add it.

The encryption key was taken from the Windows app I believe, I thought it was universal at the time. It's very difficult for me to add support for devices I don't own as there isn't a source of example backups I'm aware of.

[sachk]

Implemented in v0.3.0: Export Options now accepts a backup password; the decoder tries Smart Switch PIN/password key derivations for messages, call logs, application data, settings, storage, and other categories (including Secure Folder-style categories), while preserving raw files. These compatibility paths are fixture-tested but need confirmation with a real password-protected/Secure Folder backup. Please reopen with the anonymized diagnostic report if your backup still fails.

[aviv926]

@sachk Hey, thanks for working on this!
I just tried exporting the data with v0.3.0 on Secure Folder backup with the backup password but it seems the data is still encrypted.
How do I provide you with an anonymized diagnostic report? I haven't seen such an option or such a file created.

By the way, I don't have permission to reopen.

[aviv926]

Is there any information I can provide to resolve the issue?