Re: One per customer

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 27608
interpreted = N
texte = Kenneth Grome at ken@simplewebstores.com said this on 2/15/00 11:12 PM>Yes, there are LOTS of non-webcat methods for *trying* to prevent people >from voting more than once, but I don't think there is any sure-fire way >of guaranteeing it ...True. DigitalSignatures from a trusted third party can help, given that party verifies id with another hard to forge form of id... basically you can only trust (people or computers) so far... or look at it the otherway and simply trust people period -- or balance the cost of your need for one per customer with a cash equivalency.If it's random people vs. pre-registered (a class, for instance, or a large group of known voters) , the pre-registered group is clearly easier. You can assign a unique key to each vistor who registers, etc.Back to just trust is likely good enough. We have a Shockwave-based app that limits multiple voting, but you CAN get around it with not too much work. Having a little obscurity (embedded in Shockwave) is a small deterent. A compiled Java App would do about as well with the general public. Real security doesn't get too far though, by obscuring computations behind code.David-------------------------------------------------------------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:

Re: One per customer (Serban Constantinescu 2000)
Re: One per customer (Vince Medina 2000)
Re: One per customer (David M. Dantowitz 2000)
Re: One per customer (Kenneth Grome 2000)
Re: One per customer (Jesse Williams Proudman 2000)
Re: One per customer (Kenneth Grome 2000)
One per customer (Chuck Rice 2000)

Kenneth Grome at ken@simplewebstores.com said this on 2/15/00 11:12 PM>Yes, there are LOTS of non-webcat methods for *trying* to prevent people >from voting more than once, but I don't think there is any sure-fire way >of guaranteeing it ...True. DigitalSignatures from a trusted third party can help, given that party verifies id with another hard to forge form of id... basically you can only trust (people or computers) so far... or look at it the otherway and simply trust people period -- or balance the cost of your need for one per customer with a cash equivalency.If it's random people vs. pre-registered (a class, for instance, or a large group of known voters) , the pre-registered group is clearly easier. You can assign a unique key to each vistor who registers, etc.Back to just trust is likely good enough. We have a Shockwave-based app that limits multiple voting, but you CAN get around it with not too much work. Having a little obscurity (embedded in Shockwave) is a small deterent. A compiled Java App would do about as well with the general public. Real security doesn't get too far though, by obscuring computations behind code.David-------------------------------------------------------------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 David M. Dantowitz

DOWNLOAD WEBDNA NOW!

Re: One per customer

2000

Top Articles:

Related Readings: