Re: Login security concept?
Guess I am not being clear.
When I navigate my browser to http:\\myserver\mypage.a5w I have in effect requested mypage.a5w from the server. The server gets to do whatever processing is needed to the page before it is ever viewed (or used) by the client. In fact it has to in the case of Xbasic grids.
If I had a Grid defined by Xbasic on this page it would be visible without any input from me other than my telling the browser to get that page. The WAS created what was needed for HTML viewing based on the Xbasic before I even got the page.
What if MD5() was not much more than a place holder that told the WAS to embedd the approprate JavaScript in the page sent to the client that would encrypt the contents of the password textbox in the dialog. This all occures before the client even gets a look at the page.
Is the MD5() function used by the WAS to create an embedded script prior to sending the page requested by the client browser, thereby adding the ability to encrypt the password on the client side. You understand that all this is done done simply by the clients initial request for the page.
Has anyone looked at the source in the browser that results following a page requested from the WAS that included the MD5() function. I'll bet it has some interesting additional scripting (not Xbasic).
:-)
Guess I am not being clear.
When I navigate my browser to http:\\myserver\mypage.a5w I have in effect requested mypage.a5w from the server. The server gets to do whatever processing is needed to the page before it is ever viewed (or used) by the client. In fact it has to in the case of Xbasic grids.
If I had a Grid defined by Xbasic on this page it would be visible without any input from me other than my telling the browser to get that page. The WAS created what was needed for HTML viewing based on the Xbasic before I even got the page.
What if MD5() was not much more than a place holder that told the WAS to embedd the approprate JavaScript in the page sent to the client that would encrypt the contents of the password textbox in the dialog. This all occures before the client even gets a look at the page.
Is the MD5() function used by the WAS to create an embedded script prior to sending the page requested by the client browser, thereby adding the ability to encrypt the password on the client side. You understand that all this is done done simply by the clients initial request for the page.
Has anyone looked at the source in the browser that results following a page requested from the WAS that included the MD5() function. I'll bet it has some interesting additional scripting (not Xbasic).
:-)
Comment