title: Why use `-t rsa -b 4096` with ssh-keygen?
body: <p>Why should I use the options, <code>-t rsa</code>, <code>-b 4096</code>, and <code>-C "myemail@example.com"</code> when creating an SSH key, <a href="https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/" rel="noreferrer">as instructed by github</a>? If I create an SSH key without these options, is it less secure? If so, why?</p>
  
  <p>What frustrates me about these options is that they're hard to remember (is it 4096 or 4095? Which flag went with the number and which went with the "rsa" value? Which flag went in front of my email? Wasn't it an uppercase letter?), and creating new keys can be a frequent activity, for example, if trying out bitbucket and gitlab, and different cloud hosting providers.</p>
  
  <p>[update]<br>
  The man page states, "The type of key to be generated is specified with the -t option.  If invoked without any arguments, ssh-keygen will generate an RSA key for use in SSH protocol 2 connections."</p>
  
  <p>Why then does the github page specify <code>-t rsa</code>?</p>