[GH-ISSUE #111] Update Opaque-ke dependency #48

Open
opened 2026-02-27 08:14:56 +03:00 by kerem · 5 comments
Owner

Originally created by @nitnelave on GitHub (Dec 23, 2021).
Original GitHub issue: https://github.com/lldap/lldap/issues/111

As part of their new API, the serializer doesn't write binary as base64 in JSON anymore. We should switch the json serializer to a json+binary-to-base64 one.

Originally created by @nitnelave on GitHub (Dec 23, 2021). Original GitHub issue: https://github.com/lldap/lldap/issues/111 As part of their new API, the serializer doesn't write binary as base64 in JSON anymore. We should switch the json serializer to a json+binary-to-base64 one.
Author
Owner

@nitnelave commented on GitHub (Feb 16, 2023):

The new versions have a different encoding of the password. This would be a pretty big breaking change, which I'll only do as part of a big release (v1.0).

<!-- gh-comment-id:1433068058 --> @nitnelave commented on GitHub (Feb 16, 2023): The new versions have a different encoding of the password. This would be a pretty big breaking change, which I'll only do as part of a big release (v1.0).
Author
Owner

@nitnelave commented on GitHub (Mar 28, 2023):

It seems the OPAQUE proposal is still being worked on (version 3.0.0-rc2). The repo has also migrated to https://github.com/facebook/opaque-ke.

Once the dust has settled and the version is stable (and we're ready for a 1.0 release), I'll make the switch (requires resetting all the passwords).

<!-- gh-comment-id:1486598958 --> @nitnelave commented on GitHub (Mar 28, 2023): It seems the OPAQUE proposal is still being worked on (version 3.0.0-rc2). The repo has also migrated to https://github.com/facebook/opaque-ke. Once the dust has settled and the version is stable (and we're ready for a 1.0 release), I'll make the switch (requires resetting all the passwords).
Author
Owner

@nitnelave commented on GitHub (Mar 31, 2023):

New proposal, to avoid having to reset all the passwords: https://docs.google.com/document/d/1Y8rVSYyZzzzjKGJOVTYVFl38pKSnUopx-cijR24IMz4/edit?usp=sharing

<!-- gh-comment-id:1492164701 --> @nitnelave commented on GitHub (Mar 31, 2023): New proposal, to avoid having to reset all the passwords: https://docs.google.com/document/d/1Y8rVSYyZzzzjKGJOVTYVFl38pKSnUopx-cijR24IMz4/edit?usp=sharing
Author
Owner

@dennorak commented on GitHub (May 21, 2025):

Is there any update on this?

<!-- gh-comment-id:2896753203 --> @dennorak commented on GitHub (May 21, 2025): Is there any update on this?
Author
Owner

@nitnelave commented on GitHub (May 21, 2025):

This is a complex task that will require careful work to be user friendly, not lose data but still be secure. Currently I don't have much development time to dedicate to LLDAP, and there are other things I want to push forward (we're working on a plugin API!)

However, if someone wants to work on it, I would gladly help design and review the code!

<!-- gh-comment-id:2896940468 --> @nitnelave commented on GitHub (May 21, 2025): This is a complex task that will require careful work to be user friendly, not lose data but still be secure. Currently I don't have much development time to dedicate to LLDAP, and there are other things I want to push forward (we're working on a plugin API!) However, if someone wants to work on it, I would gladly help design and review the code!
Sign in to join this conversation.
No milestone
No project
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.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#48
No description provided.