From: Yehuda Sadeh <yehuda@inktank.com>
To: Florian Haas <florian@hastexo.com>
Cc: Wido den Hollander <wido@widodh.nl>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: URL-safe base64 encoding for keys
Date: Tue, 3 Jul 2012 08:04:03 -0700 [thread overview]
Message-ID: <CAC-hyiHXV448LMT0qkO2hvpaHw6R4WSu1rvy5L08QeABDLhjww@mail.gmail.com> (raw)
In-Reply-To: <CAPUexz8ThDn+pfqLT1azRMbHeQZP_q-_yD3O-10C=mZ5NnwYpw@mail.gmail.com>
On Tue, Jul 3, 2012 at 8:00 AM, Florian Haas <florian@hastexo.com> wrote:
> On Tue, Jul 3, 2012 at 2:22 PM, Wido den Hollander <wido@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.:
>>
>> addStoragePool?uri=rbd://user:cephxkey@monitor.addr/poolname
>>
>> If 'cephxkey' contains a / the URI parser in Java fails (java.net.URI) and
>> splits the URI in the wrong place.
>>
>> For base64 there is a specification [0] that describes the usage of - and _
>> instead of + and /
>>
>> Is there a way that we change the bits in src/common/armor.c and replace the
>> + and / for - and _?
>
> 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 alternative
encoding. If you still have some old access keys, just replace them.
Yehuda
next prev parent reply other threads:[~2012-07-03 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 12:22 URL-safe base64 encoding for keys Wido den Hollander
2012-07-03 15:00 ` Florian Haas
2012-07-03 15:04 ` Yehuda Sadeh [this message]
2012-07-03 17:23 ` Florian Haas
2012-07-03 17:25 ` Yehuda Sadeh
2012-07-03 15:35 ` Tommi Virtanen
2012-07-03 19:18 ` Wido den Hollander
2012-07-04 12:46 ` [PATCH] Generate URL-safe base64 strings " Wido den Hollander
2012-07-04 15:16 ` Sage Weil
2012-07-04 16:10 ` Wido den Hollander
2012-07-04 16:18 ` Sage Weil
2012-07-05 13:31 ` Wido den Hollander
2012-07-05 14:31 ` Sage Weil
2012-07-06 8:48 ` Wido den Hollander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC-hyiHXV448LMT0qkO2hvpaHw6R4WSu1rvy5L08QeABDLhjww@mail.gmail.com \
--to=yehuda@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=florian@hastexo.com \
--cc=wido@widodh.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.