[TwoD]

or type javascript:window.open().document.write(document.g etElementsByTagName('html')[0].outerHTML) in the url field... took just a few seconds to break it...
Don't know how it's done, try asking them lol

[Sabu]

Originally Posted by chriswatts

Can't seem to disable the view source command but while looking to see how other sites that use the same web server as me have linked back to the server I noticed this site seems to have found a way of returning a warning message instead of the main site code. Don't know how they did it.

Haha.. yes, a clever plan, but it's been done before.

Hint: open the source code again. Ignore the warning. Scroll DOWN.

[TwoD]

Haha! How could I have missed that

[Rajab]

I think your problem can be solved with this software

http://www.weblockpro.com

You can lock the contents of your site with a single click and of course there are lots of option too.

[Sabu]

Look at his source code. It's a simple javascript:eval code, once again.

It's not even double encoded except for the javascripts in the header (which anyone could paste into a decoder, found across the internet). FireFox's DOM Object Inspector can let you export the generated xml of the body. The other features - (supposed) link masking, and anti-right-click, unselector, unprinter and the 'screenshot button detector' (which probably only works in IE, or at least not firefox) are simple javascripts in the header, probably taken from various online depositories.

Source encryption, unless you've got a really good custom encoding system, just isn't worth the time. If someone wanted to steal your frontpage-5 masterpieces, there's not much you can do to stop them.

Your content? They could..

• Type it all out manually
• Decode the source
• select and copy
• take a screen shot, then scan through an OCR (this is getting serious here)

[TwoD]

I can't believe this guy, he actually dares people to try to find the source.
I'm going to mail him the entire source code just to show him how lame it is..

[Sabu]

Woah.. ok, looking through the header scripts I just might have to take back my crackability comment above.. This is one tough nut to crack, very clever.

[edit].. ok, I'm changing my mind again just rip all the code, change a few "evals" to "document.write"s and Bob's your uncle.

[TwoD]

Don't think it will be that hard to crack. I bet the escaped string contains a decompressor. (the browser needs to read the code!)
I've seen these scripts before and the last one I cracked took about 3 minutes...

[sixabat]

i just tested out over 1000 ways to keep hide my js code, but all them crackable at finally!
just this can work fine! ( hide ur js code with ajax) really great and new

http://www.alilg.com/blog/how-to-pro...x-post-20.html

[Nico]

^^ Here's the "hidden" javascript code from the demo.

Code:

function mouse_move_js(e)
{
	if(document.all)e = event;
	if (e.target) _s = e.target;
	else if (e.srcElement) _s = e.srcElement;
	mouse_x = e.clientX;
	mouse_y = e.clientY;
	
	var HDOC = "Welldone, Javascript is stay alive at this page";
		HDOC += "(Try to move your mouse on this page) <br>Mouse Xposition:"
		HDOC += mouse_x+" Mouse Yposition:"+mouse_y;
		
	document.getElementById('POS').innerHTML =  HDOC
};

var count = 0;
function timer()
{
	document.getElementById('COR').innerHTML =  "Chronometry: "+count;
	count++;
	setTimeout(timer,10);
}
timer();

document.onmousemove = mouse_move_js;

You can NOT hide your source code. When will people understand?

EDIT:

I'm going to close this now. It's old and cannot be done.