 #-    Key("a-bunch-of-base64-w-encoded-stuff")
 #- Your code is missing the first 5 and the last 2 characters. Here, I think
 #- perfect compatability with C++ is important.
+#**
+#** author: Tom Roeder
+#** email: tmroeder@google.com
+#** date 2014-07-12T09:11:00-0700
+#**
+#-- Will fix.
+#--
+
  
 -// SignerName returns a user-readable name of the signing key.
 -func (k *Keys) SignerName() string {

#- Is zeroBytes() just wishful thinking in a garbage collected language? I
#- suppose we might as well make the effort.
#-
 }
diff --git a/go/src/cloudproxy/tao/keys.pb.go b/go/src/cloudproxy/tao/keys.pb.go
index c750ca8..9cfef8d 100644

#- programs, since programs don't suddenly change languages. On the other hand,
#- there might be keys that are shared between programs.
#-
#**
#** author: Tom Roeder
#** email: tmroeder@google.com
#** date 2014-07-12T09:11:00-0700
#**
#-- I should have explained this in a comment to avoid confusion. I'll add the
#-- comment, but here's the explanation: the C++ code has methods that do
#-- serialization and deserialization with password using the OpenSSL methods
#-- that create a PKCS8 encrypted PEM structure for the private key. However, Go
#-- already has code to encrypt PEM; it's in crypto/x509. so, rather than doing
#-- that in my code, I provide a way to produce the DER for the key and let the
#-- make the call to the x509 PEM encryption routines. I believe this ends up
#-- with the same structure and will be readable by OpenSSL using the same
#-- methods, but I didn't look into it closely. I'll do that.

 
-// CrypterPath returns the path to the encryption key, if any.
-func (k *Keys) CrypterPath() string {
