On 2017-02-05 at 19:57 +0100, Stef Bon wrote: > Hmm, this is remarkable. Following RFC's strictly is one of the rules > when developing software. Without taking a stance on this particular issue reported against OpenSSH: No, following RFCs is a good default stance, unless and until you have a good reason to do otherwise. RFCs are not laws and they're not flawless. Sometimes it's right to break them. I'm one of the maintainers of Exim. That software handles a lot of mail. Sometimes we provide options to ignore RFC limits or act against them. Sometimes we make the default be explicitly against RFC and provide an option for folks to be compliant if they really want. Good engineering involves analysis of consequences and making judgement calls, not just doing whatever someone else managed to get written down. > Nobody interested? It's the weekend. You mailed on a Saturday and are chasing on a Sunday, disappointed that nobody has jumped on it already? Wait a couple more days before making such conclusions, let the OpenSSH maintainers have a chance to (1) enjoy their weekends, stress-free; (2) get around to it sometime in the week. If you want 24x7 support, you generally need to _pay_ for it. -Phil _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
