EC2 signature inconsistency
Bug #1022749 reported by
flaviamissi
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
goamz |
Fix Released
|
Critical
|
Gustavo Niemeyer |
Bug Description
Hi,
I'm trying to run some commands with goamz on an openstack installation.
Openstack have an implementation for the EC2 api, but I'm having an issue with the generated signature, I know, it could be a bug of openstack's api, but it isn't, I can use boto and a lot of other stuff that depends on this, including juju (also with boto).
The problem is that the generated signature doesn't match with the one that openstack is expecting. It is important to notice that openstack generates the expected signature based on boto's code[1].
[1] https:/
To post a comment you must log in.
Hey Flavia,
There's likely something wrong indeed, probably with the handling of +. James H. reported the same thing elsewhere.
If it's not asking too much, can I ask you for a few details:
1) The private and secret keys (*)
2) The signature generated by boto
(*) Please generate a new pair before posting in the bug.
This would be hugely helpful.
Thanks!