haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/react/features/e2ee/actions.js

17 lines
318 B
JavaScript
Raw Normal View History

e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
// @flow
e2ee: stage 2 Adapt to E2EE changes in lib-jitsi-meet. Notably: --- e2ee: introduce per-participant randomly generated keys This the second stage in our E2EE journey. Instead of using a single pre-shared passphrase for deriving the key used for E2EE, we now establish a secure E2EE communication channel amongst peers. This channel is implemented using libolm, using XMPP groupchat or JVB channels as the transport. Once the secure E2EE channel has been established each participant will generate a random 32 byte key and exchange it over this channel. Keys are rotated (well, just re-created at the moment) when a participant joins or leaves. ---
2020-05-07 09:54:02 +00:00
import { TOGGLE_E2EE } from './actionTypes';
e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
/**
e2ee: stage 2 Adapt to E2EE changes in lib-jitsi-meet. Notably: --- e2ee: introduce per-participant randomly generated keys This the second stage in our E2EE journey. Instead of using a single pre-shared passphrase for deriving the key used for E2EE, we now establish a secure E2EE communication channel amongst peers. This channel is implemented using libolm, using XMPP groupchat or JVB channels as the transport. Once the secure E2EE channel has been established each participant will generate a random 32 byte key and exchange it over this channel. Keys are rotated (well, just re-created at the moment) when a participant joins or leaves. ---
2020-05-07 09:54:02 +00:00
* Dispatches an action to enable / disable E2EE.
e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
*
e2ee: stage 2 Adapt to E2EE changes in lib-jitsi-meet. Notably: --- e2ee: introduce per-participant randomly generated keys This the second stage in our E2EE journey. Instead of using a single pre-shared passphrase for deriving the key used for E2EE, we now establish a secure E2EE communication channel amongst peers. This channel is implemented using libolm, using XMPP groupchat or JVB channels as the transport. Once the secure E2EE channel has been established each participant will generate a random 32 byte key and exchange it over this channel. Keys are rotated (well, just re-created at the moment) when a participant joins or leaves. ---
2020-05-07 09:54:02 +00:00
* @param {boolean} enabled - Whether E2EE is to be enabled or not.
e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
* @returns {Object}
*/
e2ee: stage 2 Adapt to E2EE changes in lib-jitsi-meet. Notably: --- e2ee: introduce per-participant randomly generated keys This the second stage in our E2EE journey. Instead of using a single pre-shared passphrase for deriving the key used for E2EE, we now establish a secure E2EE communication channel amongst peers. This channel is implemented using libolm, using XMPP groupchat or JVB channels as the transport. Once the secure E2EE channel has been established each participant will generate a random 32 byte key and exchange it over this channel. Keys are rotated (well, just re-created at the moment) when a participant joins or leaves. ---
2020-05-07 09:54:02 +00:00
export function toggleE2EE(enabled: boolean) {
e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
return {
e2ee: stage 2 Adapt to E2EE changes in lib-jitsi-meet. Notably: --- e2ee: introduce per-participant randomly generated keys This the second stage in our E2EE journey. Instead of using a single pre-shared passphrase for deriving the key used for E2EE, we now establish a secure E2EE communication channel amongst peers. This channel is implemented using libolm, using XMPP groupchat or JVB channels as the transport. Once the secure E2EE channel has been established each participant will generate a random 32 byte key and exchange it over this channel. Keys are rotated (well, just re-created at the moment) when a participant joins or leaves. ---
2020-05-07 09:54:02 +00:00
type: TOGGLE_E2EE,
enabled
e2ee: add UI elements * Add dialog to set the E2EE key * Use the Redux action / middleware to update the key even when set through the hash parameter * Cleanup URL after processing the key so it's not recorded in browser history
2020-04-16 11:26:44 +00:00
};
}