Securing client-side javascript
- From: davidr@xxxxxxxxxxxxxx
- Date: 2 Aug 2006 08:29:15 -0700
I have a question. Is javascript that is ran 100% on the client-side
and never does any postback/callback to the server hack proof? A user
can open the source code look at it, but is there a way for him to
change it so it does what it isn't supose to do. For example,
you use the javascript to disable/enable buttons on an .aspx page.
Would it be easy for someone to change the javascript to decide which
buttons get enabled/disabled? I know you can use validation on
textboxes to prevent <script></script> to get ran on the client side,
is there any other way though? This is new to me so I look forward to
people's opinions on security for javascript. Thanks,
David
.
- Follow-Ups:
- Re: Securing client-side javascript
- From: Scott M.
- Re: Securing client-side javascript
- Prev by Date: Re: Setting Time Zone
- Next by Date: Re: Securing client-side javascript
- Previous by thread: (2.0) Membership not working anymore after deployment
- Next by thread: Re: Securing client-side javascript
- Index(es):
Relevant Pages
|