Make dumpRSAPublicKey also accept a public key in PEM format

tests/devkeys/create_new_keys.sh

 #!/bin/bash
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 #
 # Generate .vbpubk and .vbprivk pairs for use by developer builds. These should
 # be exactly like the real keys except that the private keys aren't secret.
 
 
 # 0 = (RSA1024 SHA1)
@@ skipping 24 matching lines @@
   local len=$(alg_to_keylen $alg)
 
   echo "creating $base keypair..."
 
   # make the RSA keypair
   openssl genrsa -F4 -out "${base}_${len}.pem" $len
   # create a self-signed certificate
   openssl req -batch -new -x509 -key "${base}_${len}.pem" \
     -out "${base}_${len}.crt"
   # generate pre-processed RSA public key
-  dumpRSAPublicKey "${base}_${len}.crt" > "${base}_${len}.keyb"
+  dumpRSAPublicKey -cert "${base}_${len}.crt" > "${base}_${len}.keyb"
 
   # wrap the public key
   vbutil_key \
     --pack "${base}.vbpubk" \
     --key "${base}_${len}.keyb" \
     --version 1 \
     --algorithm $alg
 
   # wrap the private key
   vbutil_key \
@@ skipping 58 matching lines @@
 
 # Create the installer keyblock for use in Developer + Recovery mode
 # For use in Factory Install and Developer Mode install shims.
 make_keyblock installer_kernel 10 installer_kernel_data_key recovery_key
 
 # CAUTION: The public parts of most of these blobs must be compiled into the
 # firmware, which is built separately (and some of which can't be changed after
 # manufacturing). If you update these keys, you must coordinate the changes
 # with the BIOS people or you'll be unable to boot the resulting images.