URL-safe base64 encoding for keys

2012-07-03 Thread Wido den Hollander
Hi, With my CloudStack integration I'm running into a problem with the cephx keys due to '/' being possible in the cephx keys. CloudStack's API expects a URI to be passed when adding a storage pool, e.g.: addStoragePool?uri=rbd://user:cephx...@monitor.addr/poolname If 'cephxkey' contains

Re: URL-safe base64 encoding for keys

2012-07-03 Thread Florian Haas
On Tue, Jul 3, 2012 at 2:22 PM, Wido den Hollander w...@widodh.nl wrote: Hi, With my CloudStack integration I'm running into a problem with the cephx keys due to '/' being possible in the cephx keys. CloudStack's API expects a URI to be passed when adding a storage pool, e.g.:

Re: URL-safe base64 encoding for keys

2012-07-03 Thread Florian Haas
On Tue, Jul 3, 2012 at 5:04 PM, Yehuda Sadeh yeh...@inktank.com wrote: FWIW (only semi-related), some S3 clients -- s3cmd from s3tools, for example -- seem to choke on the forward slash in radosgw auto-generated secret keys, as well. With radosgw we actually switch a while back to use the

Re: URL-safe base64 encoding for keys

2012-07-03 Thread Yehuda Sadeh
On Tue, Jul 3, 2012 at 10:23 AM, Florian Haas flor...@hastexo.com wrote: On Tue, Jul 3, 2012 at 5:04 PM, Yehuda Sadeh yeh...@inktank.com wrote: FWIW (only semi-related), some S3 clients -- s3cmd from s3tools, for example -- seem to choke on the forward slash in radosgw auto-generated secret

Re: URL-safe base64 encoding for keys

2012-07-03 Thread Wido den Hollander
On 07/03/2012 05:35 PM, Tommi Virtanen wrote: On Tue, Jul 3, 2012 at 5:22 AM, Wido den Hollander w...@widodh.nl wrote: CloudStack's API expects a URI to be passed when adding a storage pool, e.g.: addStoragePool?uri=rbd://user:cephx...@monitor.addr/poolname If 'cephxkey' contains a / the