title: How to circumvent "apt-key output should not be parsed"?
body: <p>I'm automating my Docker installation. Something like this:</p>
  
  <pre><code>if apt-key fingerprint 0EBFCD88 | grep "Key fingerprint = 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88" &gt; /dev/null
  then
    # proceed
  fi
  </code></pre>
  
  <p>This worked fine in older versions of <code>apt-key</code>, but recent versions have two issues:</p>
  
  <ol>
  <li>A different output format: I can hack around that</li>
  <li><p>A warning:</p>
  
  <pre><code>Warning: apt-key output should not be parsed (stdout is not a terminal)
  </code></pre></li>
  </ol>
  
  <p>Clearly, I can hack around this as well, just redirect <code>stderr</code> to <code>/dev/null</code>. It just made me curious:</p>
  
  <p><strong>How do these fine folks suggest I verify my key fingerprints?</strong> Or am I getting this fundamentally wrong by wanting to automate it, does that defeat the point? (I think not, since I still manually lifted the expected fingerprint from the website, but feel free to tell me otherwise...)</p>