- From: Joel Merrick <
>
- To:
- Subject: [chef] Re: Re: Re: Why port 444 for openid_url?
- Date: Sat, 22 Aug 2009 17:01:24 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jkYWVWnoU77qQpNchF0YKzRikARnsiMBd674JyX8i7NnIZgu/QNDZWtNgXcfb2voJa 5kA1LWyL8e+tXbUUHXxpFQQSu25GOvDjVh9G7coVMxLpYTzWR+fBKntNnYANPq+g705u dE6dyo3unZzyhha30LGDI3AwxgjZXm5tsh0oc=
On Sat, Aug 22, 2009 at 3:54 PM, Claus
Divossen<
>
wrote:
. We are using Chef on an internal site, behind
>
firewalls with no direct internet access, and I was quite annoyed that I
>
had to set up an OpenID server just to log in to the admin interface.
Same here, I can't wait for 0.8.0 to hit the shelves.
--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
Archive powered by MHonArc 2.6.16.