Comments by "zixuan zhao" (@zixuanzhao6043) on "ByteByteGo" channel.

  1. DH alone is prone to man-in-the middle attack. So the certification verification is vitally important which the video doesn't cover much. Basically the server send a signature which is some private-key encrypted digestion of server identity information. The client then verify the public key through chain-of-trust by layers of authorities that issue certifications (system root authority is trusted unconditionally unless your local system is messed up). Using the verified public key the client decrypt the signature and compare the result to the digest generated through the negotiated digest/hash algorithm. If everything checks out, the server identity is trusted because only the private key owner is able to generate that signature.
    2
  2. call back
    2
  3. so the validation process when first fetch the salt then hash the combination of pwd+salt, does this happen at the client side or server side?
    1
  4. what about dealing with producers, kafka copy data to page cache directly from nic buffer?
    1
  5. So how's the bank evolved?
    1
  6. why there's java-vm but no python-vm or ruby-vm?
    1
  7. A snapshot of the data doesn't include the new row, so why non-repeatable (backed on snapshot) reads still sees fantom data?
    1
  8. so basically quic is another transport layer protocal that's parallel to udp/tcp, but also based on udp?
    1
  9. + cherry pick plz
    1
  10. +Chaos Engineering
    1
  11. This query actually does not need to join customers table since all the fields are present in the orders table already. (unless there are invalid / dirty customer_id data in the orders table and you want to filter them out)
    1
  12. how can it be stateless if authentication is needed? for example we need tokens and cookies right?
    1
  13. what about least errors
    1
  14. so what's diff between rolling and canary?
    1
  15. so what's the difference between MVC and MVP?
    1
  16. what about consistency
    1