jfinn/ljm_j1 - Gitea: Git with a cup of tea

作者	SHA1	備註	提交日期
jfinn	94c76c725a	auto commit v2	2 年之前
jfinn	b82d47af4d	auto commit v2	2 年之前
jfinn	dba5aabd09	export log and trace	2 年之前
jfinn	7092529f74	auto commit v2	2 年之前
jfinn	556cd0c729	auto commit v2	2 年之前
jfinn	41112b8733	auto commit v2	2 年之前
jfinn	8d414dd523	auto commit v2	2 年之前
jfinn	57fc9ad404	auto commit v2	2 年之前
jfinn	83df59ff35	auto commit v2	2 年之前
jfinn	c4c90166b6	auto commit v2	2 年之前
jfinn	565a4f6788	c1	2 年之前
tmoldovan8x8	751b363080	feat(e2ee) add ability to verify participants using a SAS mechanism It implements SAS verification as per the Matrix spec, adapted to our environment.	2 年之前
titus.moldovan	5c23a28087	fix(e2ee) adds promise to map when sending key onParticipantPropertyChanged	3 年之前
Saúl Ibarra Corretgé	6bb981532d	fix(e2ee) removed no longer needed code	3 年之前
Saúl Ibarra Corretgé	526bd5a94c	chore(lint) tame the new linter	3 年之前
Saúl Ibarra Corretgé	c24130622e	chore(deps) adapt to logger package rename	3 年之前
tmoldovan8x8	afc006e99a	feat(e2ee) add ExternallyManagedKeyHandler	4 年之前
tmoldovan8x8	dd902dd33d	fix(e2ee): destroys olm session on disabling e2ee	4 年之前
tmoldovan8x8	49c4e75f37	bugfix(e2ee): frees olm session and rotates key when remote participant disabled e2ee	4 年之前
tmoldovan8x8	2b94da12e8	feat(e2ee): makes olm sessions initialisation lazy	4 年之前
Saúl Ibarra Corretgé	c77487685e	feat(e2ee) log Olm version	5 年之前
Saúl Ibarra Corretgé	b65b1784df	feat(e2ee) publish olm id key in presence	5 年之前
Saúl Ibarra Corretgé	b5aeba27b9	feat(e2ee) emit PARTICIPANT_E2EE_CHANNEL_READY also for the initiator	5 年之前
Saúl Ibarra Corretgé	25f08f97c3	e2ee: sync ratchetted key with olm layer	5 年之前
Saúl Ibarra Corretgé	735c30ec4f	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.	5 年之前