#584 closed enhancement (wontfix)
Implementation of API for crypto modules
Reported by: | Benoit Gschwind | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 2.0 |
Component: | core | Version: | trunk |
Keywords: | Cc: |
Description
The state encrypted connection is not rely know but discussion was started on #198, but at the moment Xpra seems to define a proper API to include modules that can encrypt connections.
This ticket intend to be fixed before implementing new crypto modules
Change History (5)
comment:1 Changed 5 years ago by
comment:2 Changed 5 years ago by
Notes:
- please also see ticket:614#comment:2, this work should allow one to disable crypto completely. So that if the user does not wish to use crypto, no packets should ever trigger any crypto code to be called
- see ticket:198#comment:25
comment:4 Changed 2 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Superseded by #1252.
The next release will scale back on the crypto modules too and drop support for pycrypto. (which looks totally unmaintained)
comment:5 Changed 2 years ago by
Milestone: | future → 2.0 |
---|
2.0 removed support for pycrypto and only supports python-cryptography, see r14512
Note: See
TracTickets for help on using
tickets.
At the moment in #198, mvrable proposed a patch that separate encryption module from the core protocol which seems to be a good way to implement encryption.
At the moment I imagine the following protocol for establishing encrypted connection:
Maybe, we have to include some message that allow the encryption module to discuss to change some encryption parameters, for example temporary encryption keys.
Taking in account this step we may implement an API.
Best regards