Are you talking about access keys in the sense of SSH keys? If so, I'd
assume Paramiko works like any other ssh client in that it talks to
the user's running ssh-agent; figuring out how SSH keys work is left
as an exercise to the reader.
If you mean some API-specific key variable, then for the purposes of a
non-working example, just saying "key='asdf1234'" isn't icky, it's
just a matter of pragmatism. Certainly we'd hope that users would take
a more portable and security-conscious approach to private string
storage, but AFAIK we have never suggested a standard for doing that,
nor is it within the scope of the project to do so.
Hopefully that answers your question :)
On Mar 19, 2010, at 7:08 PM, "[email protected]"
<[email protected]> wrote:
On Mar 19, 2010, at 6:20 PM, Tom Davis wrote:
See: git-format-patch
Cool, thanks.
Now, looking at my patch, I realize that I had also changed the
example to use my "access key" file that I store in ~/.ssh, that
I've used with other cloud access libraries I've used.
It's just a common place to put access info that lets you distribute
code without worrying about accidentally leaving an access key in it.
Would that type of thing be OK to add to the example, or could I add
another example showing how I use it, or something?
I'm not sure if there's a "usual" way of storing access keys that
people commonly use with libcloud. Coding it directly into the
source is just icky.
Thanks,
S
