title: How does browser generate symmetric key during SSL handshake
body: <p>I have a small confusion on SSL handshake between browser and server in a typical https web scenario: </p>
  
  <p>What I have understood so far is that in the process of SSL handshake, client (browser in this case) encrypts a randomly selected symmetric key with the public key (certificate received from server). This is sent back to the server, server decrypts it (symmetric key) with the private key. This symmetric key is now used during rest of the session to encrypt/decrypt the messages at both the ends. One of main reasons to do so is given as faster encryption using symmetric keys. </p>
  
  <p><strong>Questions</strong></p>
  
  <p>1) How does browser pick and generates this "randomly" selected symmetric key? </p>
  
  <p>2) Do developers (or/and browser users) have control on this mechanism of generating symmetric keys? </p>