Skip to main content
Inspiring
July 11, 2009
Answered

Does Dreamweaver protect Post data (email addresses) when sending forms?

  • July 11, 2009
  • 1 reply
  • 1424 views

I'd like to know how to prevent lurkers from being able to intercept email addresses from the Registration forms (POST) as they are submitted from my site. I'm not worried about harvesting my address on my site, I think that problem is covered. But I am concerned that those who register on my site are not giving up their information. How do I prevent that?

This topic has been closed for replies.
Correct answer David_Powers

Only you can be the judge of whether you should be concerned. If the information is something that you would happily send by email, there's nothing to worry about. If the information is more sensitive, you should store the information directly into a database, and then retrieve it directly from the database.

1 reply

Participating Frequently
July 11, 2009

Dreamweaver does not and can not protect data from eavesdroppers. You need to use HTTPS if you are concerned about this.

Inspiring
July 11, 2009

Let me ask this then: Should I be concerned with this or am I wasting time.

Nothing here is financial or anything.

Inspiring
July 12, 2009

I agree with David. I'm no security expert, but it seems to me that eavesdropping techniques are much too much effort for thieves to use to capture email addresses. There are too many simpler ways to harvest them. Eavesdropping is usually used to steal more personal info like login credentials, credit card info, and more personal data. I wouldn't worry about it. Account creation forms and login forms may be a different story.


Thanks bregent,

I pretty much always do what David tells me to do and it always works out,

so...

These are, in fact registration forms so students and teachers can set up

their accounts on the website. But it is only later that they begin to input

data about themselves. At that point I'm using a recordset to grab their id

number and removing all other personal stuff from the forms, then logging

them out of the Session var and tracking them with cookies as per what I've

picked out of Snyder and Southwell's book on php security.

We're expecting a pretty good following and I just don't want to let anyone

down by stupidly ignoring any 'obvious' security holes. But even then it

really only amounts to some 'creative writing' and their personal intersts.

I'll keep this email so, if it turns out badly, I'll blame you and David.

Brian