|why base64 for import_key_pair?||Waldemar Kornewald||5/9/11 10:22 AM|
is there a good reason for not automatically base64-encoding the key within the import_key_pair() method? Why should the caller of the method do it?
|Re: why base64 for import_key_pair?||Mitchell Garnaat||5/9/11 10:25 AM|
The ImportKeyPair request accepts keypairs in three different formats:
So, I don't think we can assume that the input needs to be base64-encoded.
|Re: why base64 for import_key_pair?||Waldemar Kornewald||5/9/11 11:14 AM|
On Mon, May 9, 2011 at 7:25 PM, Mitchell Garnaat <mi...@garnaat.com> wrote:
This is what the AWS documentation says about the "PublicKeyMaterial" parameter:
"The public key. You must base64 encode the public key material before
I tried importing a key via the OpenSSH public key format and also via
|Re: why base64 for import_key_pair?||Mitchell Garnaat||5/9/11 4:26 PM|
Yes, you're right. It seems that they expect all keys material, regardless of format, to be base64-encoded prior to sending. So, I think it makes sense for boto to do that for the user. That's what we do with user data, etc.
I'll make this change tonight or feel free to send a pull request. Thanks,
|Re: why base64 for import_key_pair?||Waldemar Kornewald||5/10/11 12:24 AM|
On Tue, May 10, 2011 at 1:26 AM, Mitchell Garnaat <mi...@garnaat.com> wrote:
I've sent a pull request.