Viewing profile — SomeOtherGuy2
SomeOtherGuy2
HN member- Joined
- Mon, Jan 30, 2012, 8:21 PM UTC
- HN karma
- 9
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About SomeOtherGuy2
No profile information was provided.
Recent public activity
-
comment
Comment #3539537
>And having read and written this particular audit line item about 29074894389734897 times in the last 15 years, let me assure you that logging is clearly an issue. Which is what I…
-
comment
Comment #3539492
Unfortunately, very little is required to be HTTP compliant. It is almost all SHOULDs and SHOULD NOTs, and is full of vagueness. Here's a quick discussion of how bad the HTTP spec …
-
comment
Comment #3539479
Now read it. Notice how it is all "SHOULD" and "SHOULD NOT". You can do whatever you want and still be HTTP compliant. Using practices that are not recommended is not the same as b…
-
comment
Comment #3539343
No, I wouldn't be 99.994% sure of that at all. In fact, I would assume that if they are suggesting that people use GET, that they are in fact not logging the query params, as any s…
-
comment
Comment #3539315
Actually, we ding you for putting sensitive information in URLs that are used in a browser. The reason is that it will then be sent to other sites in the referrer header. When it i…
-
comment
Comment #3539283
Would you care to point out where in the HTTP RFCs it requires the use of certain methods for certain operations? The reality is, you can do whatever you like as far as HTTP is con…
-
comment
Comment #3539262
You are very confused. SSL is used to encrypt transmission between the browser and web server. Of course the web server decrypts the data it receives, otherwise it wouldn't be able…
-
comment
Comment #3539034
I addressed why what gets in logs doesn't matter: if their server is compromised you have to assume you are boned anyways. And I don't understand why is your comment would be talki…
-
comment
Comment #3539019
I'm not saying it is a nice API, or that it is in any way a REST API. Just that unless I am missing something, it is HTTP compliant.
-
comment
Comment #3538617
>If you're using SSL then form data in a POST request will be encrypted So will everything else, including the URI being requested, and thus the query string in it. Which is why it…
-
comment
Comment #3538581
Custom headers do not REQUIRE a prefix. So the lack of prefix does not make it non-compliant. In fact, the HTTP RFC doesn't even say they SHOULD have a prefix. And RFC822 which def…
-
comment
Comment #3538481
You have no way of knowing what they log and don't log. If their server logs are compromised, you should be assuming their username/password database was as well. And HTTPS request…
-
comment
Comment #3538446
In what way is it not compliant?
-
comment
Comment #3538436
No they aren't sent plain-text: > https://subdomain.sharefile.com/rest/getAuthID.aspx Notice the https. The facepalm is just that there's no additional security in using POST vs GE…
-
comment
Comment #3534529
>Free Software is not a gift Yes it is, that is what free means. Check a dictionary. >Free Software, as advocated by the FSF and many others The FSF doesn't actually get to re-defi…
-
comment
Comment #3533392
They didn't. They just tried to store data on EBS volumes, you know, like they are supposed to. But EBS performance is very bad, and incredibly variable. So they would end up getti…
-
comment
Comment #3533362
Because of the cloud fad. People have always made bad IT decisions based on the flavor of the month. They still do.