Dear Arne,
Thank you for your speedy reply.
I understood. I'll consider hosted app too.
But if making and running binary of JavaScript become available, I
don't know about how to accomplish them technologically, I think that
more developers and companies will make more apps for Chrome Web
Store.
Thank you again.
emmettoc
On 8月21日, 午前6:23, Arne Roomann-Kurrik <
kur...@chromium.org> wrote:
> You can use obfuscation to try and hide them from casual attempts, but
> generally keeping API keys secret in client software is extremely difficult
> (or impossible) to do if a user has root access to their machine.
>
> Alternatives exist, though - for example all the Google APIs accept
> "anonymous" as the consumer token/secret when accessing them with OAuth.
> You can also run a web service which stores your keys on your server and
> proxies requests from the extension to the APIs you use.
>
> If you have a more specific implementation question, I'm happy to try and
> help come up with a solution.
>
> ~Arne
>
> On Fri, Aug 20, 2010 at 1:29 AM, emmettoc <
creepyman2...@gmail.com> wrote:
> > Hello,
>
> > I'm interested in coming Chrome Web Store and looked through a
> > developer's guide.
>
> > When I release a packaged app, how can I protect my source codes,
> > which will contain some secret information, for example API keys? I
> > tried to read source codes of some chrome extensions and I could. Some
> > of them have raw API keys.
>
> > Thank you.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Chromium-extensions" group.
> > To post to this group, send email to
chromium-extensi...@chromium.org.
> > To unsubscribe from this group, send email to
> >
chromium-extensions+unsubscr...@chromium.org<
chromium-extensions%2Bunsubscr...@chromium.org>
> > .