Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #33401

Re: JavaScript code security

Newsgroups comp.lang.javascript
Date 2017-05-24 14:26 -0700
References (5 earlier) <422bich7hemhuhdr77fb58jfsprigttbin@4ax.com> <0d8bb805-6013-4c48-9081-07d74b848e33@googlegroups.com> <XnsA77FC4786B0C2eejj99@194.109.6.166> <94d71d2a-19e0-4381-8cbe-39127e422383@googlegroups.com> <XnsA77FEB382A340eejj99@194.109.6.166>
Message-ID <739c08be-d0dd-4890-b7ec-d59545f0aeae@googlegroups.com> (permalink)
Subject Re: JavaScript code security
From justaguy <lichunshen84@gmail.com>

Show all headers | View raw

On Wednesday, May 24, 2017 at 5:08:13 PM UTC-4, Evertjan. wrote:
> justaguy  wrote on 24 May 2017 in
> comp.lang.javascript: 
> 
> > On Wednesday, May 24, 2017 at 1:18:53 PM UTC-4, Evertjan. wrote:
> >> justaguy  wrote on 24 May 2017 in
> >> comp.lang.javascript: 
> >> 
> >> >  I vaguely recall a technique to prevent such hacking?
> >> 
> >> >  That's
> >> 
> >> "What's" ?
> >> 
> >> > the name of it?  Thanks. 
> >> 
> >> Using your intelligence.
> >> 
> > 
> > To prevent cross domain (server) form posting, one method seems to find
> > the header info of the http request to determine where the request comes
> > from and if it's not from the same domain/server then reject the FORM
> > posting. 
> 
> The posting is not froom another server, but from the client,
> and the header can be manipulated.
> 

I was referring to the posting from a web browser (a user agent) on another server, but if it were from the same server (say, I'm the owner of this server), then if another party is able to add file to or change any file on this server that would mean my server has been compromised.  About "the header can be manipulated", then, this technique of knowing where the FORM request comes from wouldn't be effective neither.  That's what you're saying, correct?

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 13:02 -0700
  Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 13:11 -0700
    Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 17:56 -0700
      Re: JavaScript code security Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-24 02:44 +0100
        Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 19:06 -0700
          Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-24 09:11 +0200
            Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-24 05:56 -0700
              Re: JavaScript code security Wally W. <ww84wa@aim.com> - 2017-05-29 14:57 -0400
                Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-30 09:41 +0200
                Re: JavaScript code security Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-06-23 10:53 +0200
                Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-06-23 13:38 +0200
            Re: JavaScript code security Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-24 14:28 +0100
              Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-24 18:07 +0200
        Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-24 06:01 -0700
          Re: JavaScript code security John G Harris <niam@jghnorth.org.uk.invalid> - 2017-05-24 14:19 +0100
            Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-24 10:01 -0700
              Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-24 19:18 +0200
                Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-24 11:39 -0700
                Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-24 23:07 +0200
                Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-24 14:26 -0700
                Re: JavaScript code security "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2017-05-25 16:26 +0200
  Re: JavaScript code security Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-24 01:12 +0200
    Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 17:15 -0700
      Re: JavaScript code security Stefan Weiss <krewecherl@gmail.com> - 2017-05-24 04:14 +0200
        Re: JavaScript code security justaguy <lichunshen84@gmail.com> - 2017-05-23 19:47 -0700
  Re: JavaScript code security Myers <xdaamanx@gmail.com> - 2017-05-29 07:54 -0700
  Re: JavaScript code security Myers <xdaamanx@gmail.com> - 2017-05-29 07:55 -0700

csiph-web