| DavidSilverlight on Oct 1, 2003 at 5:08:08 AM (# 731) Hmmmm. A Security Company. I think that it should be possible not to let them see the source code. Perhaps you can create some functionality to hide the code!!!! Maybe through encrypting it, disabling the right mouse click or some method like that. Perhaps somebody will have some suggestions as to how to hide HTML/Script here. I know for a fact that it is possible!!!!! In fact, I would bet Holophrastic's life on it!!!! RobinAnn on Oct 1, 2003 at 6:53:41 AM (# 732)Did I just kill this thread? I really didn't want to go back and read every post. But I will.
I have a simple script you can right click on it here to see - I was hoping there was something else I could do. To add to what I've got in place.
http://www.third-rail.net/robin-ann/eximius
The site is in programming beta - I like the idea of encryption - thanks! Terry Young on Oct 1, 2003 at 7:30:42 AM (# 733) This message has been edited.Ahem.....
forget it...
Escape the WWW's files-from-server-to-client model.
If you're catering windows users, use Remote Desktop Web Connection. The registry of the "server" which the "clients" connect to could be altered so that the connected users are restricted receive intended "contents".
This, of course, is a completely different area. In fact, I'm currently on a collaborative project that involves letting users try trial versions of applications without actually installing it in their own machines. They would just connect to the server and try for themselves, through an account specifically created for this purpose...
But to think of it, remote desktop web connection isn't really for you to display web pages. You're basically logging on to the server. This has little to do with "hiding HTML source code" becuase once you're logged on, it's unlikely that you will be still served with HTML. Like in our case, you log on, you have no access to taskbars and the desktop, everything is restricted, the intended app runs on startup when you log in, and logs out automatically once you close the application...
Otherwise, I would forget it... MHenke on Oct 1, 2003 at 7:35:36 AM (# 734)> Did I just kill this thread? Nope. This one is immortal, everlasting, undying, ceaseless, deathless and unremitting. Apart from that, it's nonvolatile and unfading (to say nothing of imperishable and eternal).
> I really didn't want to go back and read every post. But I will. Yeah, do so. You'll learn much more than how to (resp why not) hide source code... ;)
Terry Young on Oct 1, 2003 at 7:47:04 AM (# 735) This message has been edited."I have a simple script you can right click on it here to see"
That's only one among the list of how to obtain a web page's source code.
Start building this list, if you're interested.
FYI, I can still use the mouse only to reveal the source code, i.e. mousedown-right (don't release), left-click OK, release mouseup-right. Viola.
I've been to where you are at right now. I've done it, and scrapped it within minutes.
...I'm more interested in the coffee...
"it must be some very a profitable source, that one would be so interested in getting to the source of it" RobinAnn on Oct 1, 2003 at 8:11:10 AM (# 736)Truthfully - I would rather keep the source open - but in the case of these clients - They think it's pretty cool.
It's really not the programming source they are after - it's thier VERBAGE. Soooooooooooooooooo The encryption will help. I could do the whole source, yes? - any easy to implement code or links thereto? Terry Young on Oct 1, 2003 at 8:24:53 AM (# 737) This message has been edited."but in the case of these clients"
but in the case of *these* clients, I'd education them some common sense that they're lacking and obviously needed...
Else, microsoft script encoder, and FYI encodes the scripts so that 1) the scripts get encoded, and 2) pages may break in other browsers.
Or, shout louder, and see if someone would actually put up something (again) and let's see if we can get the source...
|