Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #22130
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail |
|---|---|
| Content-Type | text/plain; charset="UTF-8" |
| Message-ID | <2214399.Af8jLJcgcz@PointedEars.de> (permalink) |
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
| Reply-To | Thomas 'PointedEars' Lahn <cljs@PointedEars.de> |
| Organization | PointedEars Software (PES) |
| Date | Fri, 22 Nov 2013 15:18:52 +0100 |
| User-Agent | KNode/4.10.5 |
| Content-Transfer-Encoding | 8Bit |
| X-Face | %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&.<b';Md8`dH6iqhT)6C^.Px|[=M@7=Ik[_w<%n1Up"LPQNu2m8|L!/3iby{-]A+#YE}Kl{Cw$\U!kD%K}\2jz"QQP6Uqr],./"?;=4v |
| Face | iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXTxa4RFk5dUWANED8PFEfy7+MGBiW+n3ZNF/QuAAACaElEQVQ4jVXUwVOcMBQG8Dc7Rc4PUntdWV2uxjDpGaGeozOp1woar4jd5t/v9wLstMwsA/ntlxdCAgUc1hjTc9/JCZfGoo3wG3HdmdAWrIJRHe7GM/TmpY5VFefuVcAkkPbLIaN8rmPmjloyZxgyR3GuJ4K0AGtJ2htz8o7yqikm759fldQXaMpbDzjKAG+8v+AugVTOPO5DOjLvGtUYQwh0CPjnVMyGd+8/GfUB5nLKJDD2aLDh5HYyMDJGDwQIo2ZmZcKbowNmAdB/AzyFhrmF2MHRb0QJJfaAnwGB6orZhoykLzJtGwF/xpYxI1dswomiUj3gTuAIqCn/4C7cULwGNBtwMTk3Y4LfKB5YUaOKBKYtpplm7u0vip8tU1NWWyI/7XdcSuIDoMt6rVHMWT0DbjHPGqDqZVSa6zleLcUTcIKLoMv3ueJluALtAo9B302zPPlrtiVScRdCjXvVh3e3JpYa/jjkuC9N+LrBMlz/eAN4eQijX2EdLo6c5tGGHwLyHFtXk89dDGHwCVhG9T0S/j55AhRZgkMCmUQXJ49TnS1wnQDvw0eAh9ICeMmEFbCnPMFzjAvsWoEWEFdYEx+S0MoUZ1gT1wId8+AF3Bl2OoEu906AUHx5VLw/gXYg/x84loOah/2UYNrgiwSwGO7RfUzVBbx/kgpckumGOi6QirtD6gkLTitbnxNol47S2jVc2vsN5kPqaAHT8uUdAJM4v/DanjYOwmUjWznGfwB7sGtAtor5BgofDuzaRj4kSQAqDakTsKORa3Q3xKi3gE1fhl71KRMqrdZ2AWNNg/YOhQyrVBnb+i+nEg4bsDA+egAAAABJRU5ErkJggg== |
| Subject | Re: How to determine and to prevent javascript being hacked? |
| Newsgroups | comp.lang.javascript |
| References | <2b5cc6d4-c970-4faa-b169-4300e2935be4@googlegroups.com> <528deb24$0$6627$9b4e6d93@newsspool2.arcor-online.net> <d9447e08-8851-4a86-9199-1cf7aeaf1faf@googlegroups.com> |
| MIME-Version | 1.0 |
| Lines | 39 |
| NNTP-Posting-Date | 22 Nov 2013 15:18:54 CET |
| NNTP-Posting-Host | a65b05f9.newsspool4.arcor-online.net |
| X-Trace | DXC=?YaMm?=N9h^AX0F2i><W:S4IUK<Cl32<Q4Fo<]lROoRQ8kF<OcfhCO[:;[^=Pn_eYQDZm8W4\YJN\YUVHKH;GI^WKL[1=F<ohU^E?189?95>XX |
| X-Complaints-To | usenet-abuse@arcor.de |
| Xref | csiph.com comp.lang.javascript:22130 |
Show key headers only | View raw
justaguy wrote:
> Christoph Michael Becker wrote:
>> You can use Chrome's built-in debugger[1] to check the actual control
>> flow.
>>
>> [1] <http://devtoolsecrets.com/>
>
> Does the F12 key do the same thing?
That is a stupid question.
,--<http://devtoolsecrets.com/>
|
| Finding the Developer Tools
|
| If Developer Tools are a complete secret to you, you may have had
| difficulty finding them!
|
| As well as a menu shortcut, you can access the Developer Tools easily
| either pressing "F12" in Windows […]
^^^^^^^^^^^^^^
FTR, it is F12 on GNU/Linux, too, and probably a number of other OSs.
It is more a matter of the keyboard layout and the browser than of the OS.
> I watched js code execution in Chrome with this window. It's likely that
> my computer has been planted with a virus that caused this issue...
It is more likely that you do not know what you are doing.
> And publicly available anti-virus program won't be able to fix it...
Most certainly it is not a virus at all, then.
--
PointedEars
Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-20 17:56 -0800
Re: How to determine and to prevent javascript being hacked? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-20 18:42 -0800
Re: How to determine and to prevent javascript being hacked? Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-21 02:57 +0000
Re: How to determine and to prevent javascript being hacked? John Harris <niam@jghnorth.org.uk.invalid> - 2013-11-21 10:50 +0000
Re: How to determine and to prevent javascript being hacked? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-21 12:14 +0100
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-21 20:25 -0800
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-22 15:18 +0100
Re: How to determine and to prevent javascript being hacked? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-22 20:08 +0100
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-22 22:15 +0100
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-22 14:50 -0800
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-23 00:16 +0100
Re: How to determine and to prevent javascript being hacked? Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-23 01:38 +0000
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-23 14:30 -0800
Re: How to determine and to prevent javascript being hacked? (Resolved) justaguy <lichunshen84@gmail.com> - 2013-11-28 11:22 -0800
csiph-web