New answers tagged

0

You need to be able to distinguish between the trusted client and the untrusted third party in order to block the third party. This means that you somehow need to find out when the trusted client connected and when the connection does not come from the trusted client. This means you need some form of authentication but it does not need to be some setup with ...


1

A proxy forwards all traffic and therefore has the possibility to also modify the traffic and thus also to modify the traffic in a malicious way, including making the client download malware or exploiting bugs in the client processing the traffic. This is definitely true for plain HTTP but is also true for HTTPS if the client does not properly check the ...


1

It sounds like what you are wanting to implement is a signed URL, similar to Amazon S3 URLs. As long as your secret is strong and secure it sounds like a reasonable way to verify the email address in a stateless fashion. At the moment you are only signing/hasing the PIN and this is an issue with your code. If I get a valid PIN/PIN_HASH combination for ...


0

No attacks from the outside are possible as long as you always use the localhost address (127.0.0.1) to connect to the server (and you only bind to that address too, just to be safe). However, malicious software which may be running on your machine can still intercept localhost connections. This is very unlikely but possible. SSL wouldn't do much good ...


Top 50 recent answers are included