This repository has been archived by the owner on Aug 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathnotes.txt
41 lines (31 loc) · 1.68 KB
/
notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
references:
https://www.cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake/
https://www.acunetix.com/blog/articles/tls-ssl-cipher-hardening/
https://thecybersecurityman.com/2018/04/25/https-the-tls-handshake-using-diffie-hellman-ephemeral/
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.sec.doc/q009930_.htm
https://www.thesslstore.com/blog/explaining-ssl-handshake/
https://www.cloudflare.com/learning/ssl/what-is-a-session-key/
https://docs.twistedmatrix.com/en/twisted-18.9.0/web/howto/using-twistedweb.html
dúvidas:
cliente fornece varias e o servidor escolhe uma aleatoriamente
licença -> token para controlo de acesso
chave em memória -> pode ser eleminada apos um determinado tempo
servidor tem dicionario em memoria com sessoes
para o user pedir a licemça, basta fazer um pedido à api? (api/license/musica)?
quem é que define o tempo da licença? cada música tem parâmetros de licença pré-definidos? ou é o cliente que os define?
diferença entre user e client? 1 user = 1 client?
como guardar as licenças de cada client/user?
as keys usadas na comunicação client-server devem ser guardadas num array ou dicionário no server?
hash chain based scheme? explique plsssss
cipher_suites = [
'DHE_AES256_CBC_SHA384','DHE_AES256_CFB_SHA384',
'DHE_AES128_CBC_SHA256','DHE_AES128_CBC_SHA384',
'DHE_ChaCha20_SHA384','DHE_ChaCha20_SHA384',
'DHE_ChaCha20_SHA256'
]
certificates db pwd: mediapwd4#
uuids:
bv7vin4xdir1ny1bkgzoevbwkc74ppeiysyhqstz
6novk8kn7idiad1bon32qvbq7rnzlh10uw15lnp5
0woft9i8rz553vttlnc33yjzcs4li1a3mtt60e8v
b7twdi1w8h9r3065rp9vowruc1dos0578qag6pet