Преглед на файлове

e2ee: update docs (#1101)

fixing some minor issues and updating the description of the behaviour
when there are decoding errors
dev1
Philipp Hancke преди 5 години
родител
ревизия
e4838d319f
No account linked to committer's email address
променени са 1 файла, в които са добавени 8 реда и са изтрити 3 реда
  1. 8
    3
      doc/e2ee.md

+ 8
- 3
doc/e2ee.md Целия файл

@@ -36,7 +36,12 @@ tag length is the default 128 bits or 16 bytes. For video this overhead is ok bu
36 36
 for audio (where the opus frames are much, much smaller) we are considering shorter
37 37
 authentication tags.
38 38
 
39
-We do not encrypt the first few bytes of the packet that form the VP8 header or the Opus
40
-This allows the encoder to understand the frame a bit more and makes it generate the fun looking garbage we see in the video. This also means the SFU does not know (ideally) that the content is end-to-end encrypted and there are no changes in the SFU required at all.
39
+We do not encrypt the first few bytes of the packet that form the VP8 payload
40
+  https://tools.ietf.org/html/rfc6386#section-9.1
41
+nor the Opus TOC byte
42
+  https://tools.ietf.org/html/rfc6716#section-3.1
41 43
 
42
-Decryption errors are handled by just forwarding the frame to the decoder. In particular that means that when receiving unencrypted video we will display it as is.
44
+This allows the decoder to understand the frame a bit more and makes it generate the fun looking garbage we see in the video.
45
+This also means the SFU does not know (ideally) that the content is end-to-end encrypted and there are no changes in the SFU required at all.
46
+
47
+Decryption errors are currently handled by inserting silence or a black frame.

Loading…
Отказ
Запис