Re: Encrypted links ...
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 26875
interpreted = N
texte = I do use the page protection stuff, but it doesn't cover all cases. All my vendors use my Virtual Business Center application that I wrote in WebCat and they all get/have to use the same templates to manage their web presence on my servers. they only way to identify what data is to be shown on the page is something like a company ID and some other identifiers. The page protection has to let them all in to the same pages so it is of no use for this function. I don't want one vendor to suss out how to look like someone else. Name and password doesn't cut it as some people manage more than one account. You have your way, and I have mine. This uses less code and bandwidth. There are other ways to skin a cat sometimes. :)ml> >I use it to keep people from hacking into sensitive areas and to keep vendors in their own areas. > >Doesn't webcat's page-level protection scheme work properly for you? That's what it was designed for -- so you would never have to worry about what's in the URL ... > > > >In additions I encrypt the parameters so they can't suss out how to change parameters to get someone else's sensitive data. > >Oh, so you're not using it, I see -- you use this technique instead. > > > >Sure they can see the results of their own link, but they can't figure out how to generate the encrypted data to come in as someone else. > >If you were using webcat's page protection mechanism, this would not be an issue, because they could not Come in as someone else without that person's username/password or other private identifying info anyways. > >But I'm sure you know that already ... :) > >================================ >Kenneth Grome, WebDNA Consultant >808-737-6499, http://webdna.net >================================ > > > > > >------------------------------------------------------------- >Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. >To end your Mail problems go to
. > >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to \|/ (. .) _________________________ooO_(_)_Ooo_____________________________ Mark Lacas mailto:mark@lacas.com Virtual Loft / Seattle HarborCam: http://www.loftcam.com/ SeattleStuff WebCommerce Community: http://www.seattlestuff.com/ ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
I do use the page protection stuff, but it doesn't cover all cases. All my vendors use my Virtual Business Center application that I wrote in WebCat and they all get/have to use the same templates to manage their web presence on my servers. they only way to identify what data is to be shown on the page is something like a company ID and some other identifiers. The page protection has to let them all in to the same pages so it is of no use for this function. I don't want one vendor to suss out how to look like someone else. Name and password doesn't cut it as some people manage more than one account. You have your way, and I have mine. This uses less code and bandwidth. There are other ways to skin a cat sometimes. :)ml> >I use it to keep people from hacking into sensitive areas and to keep vendors in their own areas. > >Doesn't webcat's page-level protection scheme work properly for you? That's what it was designed for -- so you would never have to worry about what's in the URL ... > > > >In additions I encrypt the parameters so they can't suss out how to change parameters to get someone else's sensitive data. > >Oh, so you're not using it, I see -- you use this technique instead. > > > >Sure they can see the results of their own link, but they can't figure out how to generate the encrypted data to come in as someone else. > >If you were using webcat's page protection mechanism, this would not be an issue, because they could not Come in as someone else without that person's username/password or other private identifying info anyways. > >But I'm sure you know that already ... :) > >================================ >Kenneth Grome, WebDNA Consultant >808-737-6499, http://webdna.net >================================ > > > > > >------------------------------------------------------------- >Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. >To end your Mail problems go to . > >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to \|/ (. .) _________________________ooO_(_)_Ooo_____________________________ Mark Lacas mailto:mark@lacas.com Virtual Loft / Seattle HarborCam: http://www.loftcam.com/ SeattleStuff WebCommerce Community: http://www.seattlestuff.com/ ------------------------------------------------------------- Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server. To end your Mail problems go to .This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Webcat
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
OT - royalty free images (2002)
SV: Mass Mail (2000)
Separate SSL Server (1997)
WebCatalog Features (1997)
Banners (1997)
more on my bbs (1997)
Referrer field to header field conversion (1997)
empty shopping cart message (1997)
no [include]s with encryption? (1998)
RE: Formulas.db + Users.db (1997)
Multiple prices (1997)
Upgrading old WebCat Database Files (1997)
Instability Problem (1999)
Bad merge format error message. (2004)
Re2: frames & carts (1997)
WebCat2b15MacPlugin - [protect] (1997)
Mem per threads (1998)
Nav. 4 probs with cart (1997)
Using the new syntax/scoping methods (2000)
[HIDEIF] inside [FOUNDITEM] (1997)