full-disclosure - Re: JavaScript exploits via source code disclosure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201005060820.53269.marc.olive@grupblau.com>
Date: Thu, 6 May 2010 08:20:53 +0200
From: Marc Olive <marc.olive@...pblau.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: JavaScript exploits via source code disclosure

El Thursday 06 May 2010 07:44:07 Ed Carp va escriure:
> We've got a lot of JQuery code that calls back-end web services, and
> we're worried about exposing the web services to the outside world -
> anyone can "view source" and see exactly how we're calling our web
> services.
>
> Are there any suggestions or guidelines regarding protecting one's
> source from such disclosure?  Thanks in advance!

Anyway, the webservices will be always exposed to the world, so anyone can 
find it's wsdl to see the exposed functionanilities and call them, willn't?

As JS is a scripting languaje, the client will always have the code, as far as 
I know. Ofuscating it will not solve the problem but mitigate it.
Maybe WS-Security will help you, google for it.

Regards,

-- 

Marc Olivé
Grup Blau

www.grupblau.com  

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/