New answers tagged http
5
Both server and client know something secret, thus they can trust that there communication isn't being altered in route. Effectively, using a connection via the shared key between them is like using SSL without the hand shake. Normally SSL would use asymmetric cryptography to a) validate one or more parties in the communication and b) establish a shared ...
4
If you aren't using HTTPS then this information could easily be picked up by anyone sitting between you and your server and reused. If you are using SSL/HTTPS to encrypt the link, then you should be fine.
0
Short answer: Yes, but not as possible as it used to be, and dependent upon how literally one takes your question.
Long answer:
I notice that you did not ask "Is it possible to carry on a TCP conversation with a spoofed IP address" - that question was ably answered by @symcbean. You specifically asked "Is it possible to pass TCP handshake with spoofed IP ...
2
Without access to the network behind one of the allowed IP addresses or access to a machine behind one of the allowed IP addresses, you can not pass a TCP 3-way handshake with a spoofed IP address.
6
Short answer: no.
Longer answer: yes, if you control a router device close to the target device (it has to be on the path between the the real source IP address and the target, and on the path between the faked IP address and the target) or if the target network/host accepts source-routed packets.
2
1) Assuming that the server is also malware free, and that you aren't subject to a Man in the Middle (MitM) attack, only the client and the server can monitor the connection. It's easy to see how the session can be monitored if client or server is compromised. MitM is the real attack vector against this.
With MitM, the attacker presents the client with a ...
4
There isn't anything inherently insecure about the method you describe. However, this isn't the proper way to prevent directory browsing. It is easy to forget to add an empty index.html or index.php file to directories especially if you are managing tens of directories.
You should instead configure your web server appropriately to turn off directory ...
2
The blank index file is indeed enough. But the proper way of doing that would be to disable directory indexing (in Apache web server you do that by not adding Indexes to vhost options).
This is because if you do that on a per-directory basis, you're liable to forget doing that for all directories you need to "protect". Also, you might come to harm if the ...
2
Security through obscurity means violating Kerckhoffs's principle, which can be summarized this way: assume all cleverness is public and keep the randomness private.
This means that your security must not be hurt by making your protocol public. On the other hand, keeping a password private is the whole point of a password.
You should be able to quantify ...
2
Let's see if we can break this down:
You're using SSL which is good. SSL encrypts all the data you send including the URL. However SSL only protects the data while it is in transit. Meaning on both the server and the client end the data may be readable.
If you have a security token (username/password, randomly generated key, or whatever) and you transmit ...
6
I'll try to answer the question itself without lecturing you on what to use and what not to use.
Taking your assumptions into account (which are quite daring assumptions, IMO)
SSL is used.
No logging anywhere.
The GUIDs aren't easily predictable.
The password is strong.
Then no, this is not security by obscurity. This is security by, well.., security. ...
1
The former format <user>:<password>@<host> is deprecated and is not supported by all major browsers, so don’t use it. However, browsers which do support it convert such a HTTP URI to a request with HTTP Basic Authentication.
So your question should rather be about HTTP Basic Authentication and URI parameters via HTTPS. And the main ...
1
According the analysis from TrendMicro this is part of Asprox botnet.
More information on:
http://rebsnippets.blogspot.com/asprox
http://www.trendmicro.com/cloud-content/us/pdfs/security-intelligence/white-papers/wp-asprox-reborn.pdf
0
Well here is how I ended up implementing CSRF:
On the first request, sets a CSRF token as a cookie. Every subsequent AJAX requests include the CSRF token as a X-CSRF-Token HTTP header.
Django has some nice documentation on how to do this cleanly with jQuery: https://docs.djangoproject.com/en/dev/ref/contrib/csrf/
Edit: Apparently. an easier technique ...
1
You're in luck! Just about 2 weeks ago I was asked the same question, and after a bit of head-scratching, I came up with the following. Please keep in mind that this is not well peer-reviewed, so we'll see how the comments and voting goes. Personally, I think it's a good technique.
1. First request
Once you receive the first request to load your ...
2
A webmaster sent me a get.php file.
So the virus download comes from a separate server, so the payload can be generated elsewhere.
And unless the conditions are met below, then you get a fake 404.
If the central virus server wants you to, you get a fake 404.
There are literally hundreds of websites out there that still have this PHP script but the 404 makes ...
Top 50 recent answers are included
