haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
jiti-meet/css/_e2ee.scss

21 lines
370 B
SCSS
Raw Normal View History

ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
#e2ee-section {
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
display: flex;
flex-direction: column;
ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
.description {
ui: making the security menu more compact
2020-06-25 13:44:17 +00:00
font-size: 13px;
ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
margin: 15px 0;
}
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
.control-row {
ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
display: flex;
flex-direction: row;
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
justify-content: space-between;
margin-top: 15px;
ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
label {
ui: making the security menu more compact
2020-06-25 13:44:17 +00:00
font-size: 14px;
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
font-weight: bold;
ref: move e2ee field into security menu
2020-06-17 10:53:46 +00:00
}
}
}