Here's a fun little utility that you can use to decode a Base64-
encoded X.509 certificate:
http://www.redkestrel.co.uk/utilities/CertDecoder.html
- Jason
On Jun 17, 2:16 pm, davew <[EMAIL PROTECTED]> wrote:
> Sorry I need more coffee today. I meant hi5, which is:
>
> hi5_public_key_st
Sorry I need more coffee today. I meant hi5, which is:
hi5_public_key_str = """0x\
009981dad8b0409e18efd8b2b0df68\
efef23232aefe0d87409889b3c20df\
9c27b62dc3af707a912e8e79188100\
8513bdd6575f75e2b491715650c51f\
f3db4629a6d1ddde42f49f5b7fb4c4\
8845f42dc4f50163e8b581cfa6c196\
1e69d29497ca0
Hi Guy,
Check out Lane's article
http://code.google.com/apis/opensocial/articles/appengine.html
It has everything you need to handle OAuth sigs. I also have the hex
code for Orkut's certificate if you need it.
-Dave
On Jun 17, 3:21 am, Guy Rutenberg <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On J
Hi,
On Jun 12, 2:45 pm, "Rohit Ghatol" <[EMAIL PROTECTED]> wrote:
> http://code.google.com/apis/opensocial/articles/appengine.html
Thanks it really helped. However, I'm stuck on parsing the x509
certificate to hex. Can you give me some pointers on how to parse
(which part of it should I convert
Hi,
I am sharing a tutorial with you which has verifying signed request as a
part of it. The tutorial is about OpenSocial app communicating with Google
App Engine (which is in python) using signed request.
http://code.google.com/apis/opensocial/articles/appengine.html
Just read the section with t
5 matches
Mail list logo