Disable View source

R

Roman

Hello to everybody,
I have some question concerning blocking view source from main menu of
IE or MF. I am able to block right click with <body
oncontextmenu="return false"> but still missing from main View->Source
Code.
Any hints ?
Regards,
Roman
 
R

RobG

Roman said:
Hello to everybody,
I have some question concerning blocking view source from main menu of
IE or MF. I am able to block right click with <body
oncontextmenu="return false"> but still missing from main View->Source
Code.
Click to expand...

You only think you can, you can't prevent that reliably at all. There
are many ways of viewing the source other than via right-click or
browser menus.

Any hints ?
Click to expand...

Yes, don't even try. Anything you publish on a web server can be viewed
and saved by someone visiting the site. If you don't want that, don't
publish it.
 
J

John Bokma

Roman said:
Hello to everybody,
I have some question concerning blocking view source from main menu of
IE or MF. I am able to block right click with <body
oncontextmenu="return false"> but still missing from main View->Source
Code.
Any hints ?
Click to expand...

Don't waste your time and don't annoy your visitors. Your source is
probably not worth to be stolen in the first place.
 
I

Ivo

Roman said:
I have some question concerning blocking view source from main menu of
IE or MF. I am able to block right click
Click to expand...

Sorry, but no, you are not.
with <body oncontextmenu="return false"> but still missing from main
View->Source Code.
Any hints ?
Click to expand...

There is no way you can hide your source from us or anybody. All you can do
is discourage people. If the browser is to display a page, the raw code must
be present on the user's hard disk, if directly not accessible from the main
menu due to scripts, frames and whathaveyou, then certainly from the
Temporary Internet Files folder, or by whatever name the cache may be known
locally.

And this little beauty of a bookmarklet restores all kinds of menus:

javascript:(function(w){for(var%20i=0;i<w.length;i++){arguments.callee(w.fra
mes);}try{function%20n(r){r.onclick=r.oncontextmenu=r.onmousedown=r.onmou
seup=null;}n(w.document);n(w.document.body);}catch(e){alert('Bookmarklet%20f
ailed:\n\n'+e.message);}})(top);

Really, it is more productive to put your energy into more fruitful
endeviours such as authoring innovative pages that people will want to come
and see, than hiding source code. If it is confidential, it doesn't belong
on the web.
 
L

Lee

Ed Jay said:
I wonder how owners of web-hosted applications are going to secure the
integrity of their ownership...
Click to expand...

They're going to run anything they don't want public on their
servers, sending only the output to the client.
 
R

RobG

Ed said:
While anyone with a will can see everything you've published and there's
nothing you can do stop that, there are several things you can do to
dissuade the casual looky-Lou from peaking at your code.
Click to expand...

What sort of threat - security or competitive - do such persons present?
How does preventing access to source code prevent anyone from
implementing a copy of your site? Getting the source code has never
been a requirement for knocking-off your competition.

I think there should be a way to hide proprietary code. The need exists
and it's going to get bigger as hosted software becomes more commonly
used.
Click to expand...

A couple of methods spring to mind - there are others:

1. Provide downloadable binary executables - failed
2. Applets (Java, ActiveX) - rare, mistrusted
3. Xwindows and suitable X-client - never got off the ground
4. CORBA/IIOP barely drew breath - total failure

I'm about to market web-hosted medical diagnostic software that employs a
few proprietary algorithms. I've taken great measures to assure the app
isn't stolen, but I know that somewhere out there is a 13-year old,
pimply-faced kid wearing big glasses and a big grin who could get the code
if the mood struck him.
Click to expand...

What will he/she do with it? How come eBay takes no precautions what so
ever? Or Google? Or even MSN? Because the value is in the service,
not the code.

You may as well complain that your competitors copied your idea of
putting in a front door to let the customers in. :)

I wonder how owners of web-hosted applications are going to secure the
integrity of their ownership...
Click to expand...

Those that try fail. Winners base their business on providing the best
service - their sites are kept up-to-date, they run efficiently in
(nearly) any browser, they offer useful content, they are open and
welcoming.
 
V

VK

Ivo said:
There is no way you can hide your source from us or anybody. All you can do
is discourage people. If the browser is to display a page, the raw code must
be present on the user's hard disk, if directly not accessible from the main
menu due to scripts, frames and whathaveyou, then certainly from the
Temporary Internet Files folder, or by whatever name the cache may be known
locally.
Click to expand...

To be fair there is a way to have View > Page Source grayed out (not
available). But it is not achievable by client-side scripting. One need
to send a right sequence of response headers from the server. It is
also not supported by all browsers, and where supported it smashes down
the browser caching mechanics.

But it is an absolute true: service is the key to success, not a copy
protection. One should go by the presumption of innocence and do not
look at *your* future visitors as a bunch of thiefs. (But still think
of them as of a bunch of experienced server hackers - it is paranoidal
and it is *not* true, but it's the way to build a secure server
solution).

It is very difficult to believe when reading Internet news :), but in
the most part these are the same people used to work for money and
respect someone else's property. The rest sign off for "shrink" (as
it's called in grocery stores).
 
R

Randy Webb

Evertjan. said the following on 1/13/2006 4:37 AM:
VK wrote on 13 jan 2006 in comp.lang.javascript:

To be fair there is a way to have View > Page Source grayed out (not
available). But it is not achievable by client-side scripting.
Click to expand...


Try this to gray it out:

<http://devrijehuisarts.org/test/noViewSource.asp>

[sorry, no clientside script]

;-)
Click to expand...

You need to update that image to say "This page has no view-source in
Internet Explorer but it does in Firefox".

Right click>View Page Source

Not of much use to you but it will give you some source code :)
 
E

Evertjan.

VK wrote on 13 jan 2006 in comp.lang.javascript:
Right, I meant similar trick, and (besides other drawbacks) IE is the
only one (at least on Windows) who buys it.
Click to expand...

I doubt FF can be fooled.
 
P

Paul Cooper

A couple of methods spring to mind - there are others:

1. Provide downloadable binary executables - failed
2. Applets (Java, ActiveX) - rare, mistrusted
3. Xwindows and suitable X-client - never got off the ground
4. CORBA/IIOP barely drew breath - total failure
Click to expand...

Takes deep breath in anticipation of flames:

Use JSP or PHP or ASP to keep the processing server side?

If the data are client side, then you're sunk - you either have to
download an application (applet, OCX or plugin), or trust your users.

There simply isn't a Javascript answer, which puts it out of scope for
this newsgroup.

Paul
 
P

Patient Guy

While anyone with a will can see everything you've published and
there's nothing you can do stop that, there are several things you can
do to dissuade the casual looky-Lou from peaking at your code.
Click to expand...

The "casual looky-Lou" most likely has no interest in your code, which
might actually be very badly written and poorly instructive.

Those determined to see your code who have even a modicum of talent will
get past your vain attempts to frustrate them.

In getting to the script, some people would answer to those asking the
question of how one sees the Javascript in the delivered document: "if
you have to ask, you probably don't need to know the answer."
 
D

Dr John Stockton

JRS: In article <[email protected]>, dated Fri, 13 Jan
2006 13:12:05 local, seen in Patient Guy

But not from other browsers?
The "casual looky-Lou" most likely has no interest in your code, which
might actually be very badly written and poorly instructive.
Click to expand...

Not necessarily so.

For example, a potential employer may wish to look at the Web site of a
potential employee, to see whether the employee appears competent,
follows accepted standards, etc. I've read that TL's site is
interesting in this respect. Likewise, a potential client might wish to
assess a possible provider of services.

My copy of W3's TIDY finds no problems with my copy of the newsgroup
FAQ; but the validator in my copy of CSELITE20 (Copyright © 1997-2000 AI
Internet Solutions. Wed, May 03 2000) finds two errors on line 715 !!
They are, however, errors I've frequently found harmless myself.
 
P

phfeenikz

serve all the content by the IE version of XMLHttpRequest
and use innerHtml to insert it into the document.

then if they do click view source all they'll see is the fetcher.
Click to expand...

Better yet use the IE, AND FF version of XMLHttpRequest.

Remember that since the source can be viewed by anyone, they can also
see the URL that XMLHttpRequest is requesting. This means anyone can
visit that URL by typing it into their address bar, and then view the
source from there. Futhermore, XMLHttpRequest will not serve up
javascript; that can only be done on the client side. The only way to
hide code on the internet is to put it in a server-side script i.e.
PHP, ASP, PERL, etc., and serve the resulting content to the user's
browser (be it via a URL, or XMLHttpRequest). XMLHttpRequest itself
won't hide the code.
 
A

askMe

Ed said:
While anyone with a will can see everything you've published and there's
nothing you can do stop that, there are several things you can do to
dissuade the casual looky-Lou from peaking at your code.

I think there should be a way to hide proprietary code. The need exists
and it's going to get bigger as hosted software becomes more commonly
used.
Click to expand...

I agree that the need exists. On the other hand, source code viewing
often helps the user. For example, I hate going to a site, filling out
some long form, posting it, then receiving a javascript error
preventing the form's submission. Viewing the source may provide
details about what went wrong (usually a missing/renamed form element
referred to by the javascript's onsubmit).
I'm about to market web-hosted medical diagnostic software that employs a
few proprietary algorithms. I've taken great measures to assure the app
isn't stolen, but I know that somewhere out there is a 13-year old,
pimply-faced kid wearing big glasses and a big grin who could get the code
if the mood struck him.
Click to expand...

Shouldn't anything that processes/transmits medical information use
https?

http://www.askblax.com
 
R

Randy Webb

askMe said the following on 1/15/2006 7:26 AM:
I agree that the need exists.
Click to expand...

And a means to protect "source code" exists. Just not for the web. And
there is no "need" for it.
On the other hand, source code viewing often helps the user.
Click to expand...

Only if the user is trying to learn how (or how not to) write code.
Other than that, viewing the source doesn't "help the user" anymore than
anything else does.
For example, I hate going to a site, filling out some long form,
posting it, then receiving a javascript error preventing the form's
submission.
Click to expand...

As well as I do. But viewing the source won't fix the error. It can only
tell me how to circumvent the js. But that still doesn't help the
*average* user.

javascript:document.forms[formName].submit();

I need the source to know the formname or the forms number in the page.
That is the only reason I need to view the source of a crappy page with
JS errors.
Viewing the source may provide details about what went wrong (usually a
missing/renamed form element referred to by the javascript's onsubmit).
Click to expand...

Unless you are emailing the webmaster to inform them how to duplicate it
and fix it, then finding the source of the error is of no use.
Shouldn't anything that processes/transmits medical information use
https?

http://www.askblax.com
Click to expand...

A better solution would be a stand-alone application that used an
internet connection to transmit data via https or some other secure
protocol would be a browser based application any day.
 
T

Thomas 'PointedEars' Lahn

RobG said:
A couple of methods spring to mind - there are others:

1. Provide downloadable binary executables - failed
Click to expand...
^^^^^^
I beg your pardon?
2. Applets (Java, ActiveX) - rare, mistrusted
Click to expand...

True, however Java applets do not require ActiveX/COM per se.
3. Xwindows and suitable X-client - never got off the ground
Click to expand...

Could you please elaborate on what you mean by "Xwindows"?


PointedEars
 
R

RobG

Thomas said:
RobG wrote:



^^^^^^
I beg your pardon?
Click to expand...

Gosh Thomas, did you decide to mark my stuff for homework? I'll reply
to just this one.

I was commenting on Ed's request to hide source code and suggesting that
supplying binary executables was one way of 'hiding' the source.

I consider it has failed because getting users to download binary files
for use over the web as a general method of providing functionality on
web sites has been tried but is extremely rare.

Most surfers won't even download plugins, they just use whatever came
with their PC and if that doesn't work, they'll go elsewhere. Some
banks used to require users to download programs to run for internet
banking which were generally only for Windows - all the ones I know of
have now switched to using open standards that work in any (modern)
browser on any platform (hurrah for that).

True, however Java applets do not require ActiveX/COM per se.
Click to expand...

I'm not suggesting that they do, I'm suggesting that ActiveX and Java
are technologies that can be used for applets. They aren't necessarily
mutually exclusive, or dependent, or the only technologies available but
they are probably the most common and best known.

Could you please elaborate on what you mean by "Xwindows"?
Click to expand...

As in "X Window System", e.g. X11. I think you knew that.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

FAQ Topic - How do I disable the right mouse button? (2010-08-13) 44
FAQ Topic - How do I disable the right mouse button? (2010-06-12) 1
FAQ Topic - How do I disable the right mouse button? (2010-04-12) 0
FAQ Topic - How do I disable the right mouse button? (2010-02-10) 1
FAQ Topic - How do I disable the right mouse button? (2009-12-16) 2
FAQ Topic - How do I disable the right mouse button? (2009-10-18) 9
FAQ Topic - How do I suppress a context menu (right-click menu)? (2012-02-22) 0
FAQ Topic - How do I disable the right mouse button? (2009-08-22) 0

Members online

No members online now.
Total: 32 (members: 0, guests: 32)
Robots: 429

Forum statistics

Threads
473,769
Messages
2,569,582
Members
45,066
Latest member
VytoKetoReviews

Latest Threads

Top