From the mentioned specification: > TCP implementations should follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. Better to look in the sources ;)
Yes, that would be concerning indeed... The author couldn't tell why he didn't manage to make run the C or python program but figured it is probably the blame of the language for some obscure reasons. He also mentioned…
You changed the problem. Postel's law is not about writing the protocol but implementing it. Sure, protocol should be designed to be as specific as possible but unfortunately these are not always defined up to that…
Following Postel's law does not mean to accept anything. The received data should still be unambiguous. You can see that in the case where ASN.1 data need to be exchanged. You could decide to always send them in the DER…
Cookie value can contain `=`, `/` and `+` characters so standard base64 encoding can be used as well :)
So, just be as conservative as possible when you produce data and as liberal as possible when you receive something. Your code will then require the least cooperation from *any* other code to be compatible with. Doing…
Ironically, this supports the message of the article :D
From the mentioned specification: > TCP implementations should follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. Better to look in the sources ;)
Yes, that would be concerning indeed... The author couldn't tell why he didn't manage to make run the C or python program but figured it is probably the blame of the language for some obscure reasons. He also mentioned…
You changed the problem. Postel's law is not about writing the protocol but implementing it. Sure, protocol should be designed to be as specific as possible but unfortunately these are not always defined up to that…
Following Postel's law does not mean to accept anything. The received data should still be unambiguous. You can see that in the case where ASN.1 data need to be exchanged. You could decide to always send them in the DER…
Cookie value can contain `=`, `/` and `+` characters so standard base64 encoding can be used as well :)
So, just be as conservative as possible when you produce data and as liberal as possible when you receive something. Your code will then require the least cooperation from *any* other code to be compatible with. Doing…
Ironically, this supports the message of the article :D