Deprecate 0.0.0.0 for Private Network Access

Re:Deprecate 0.0.0.0 for Private Network Access by otabdeveloper4 on Wednesday August 07, 2024 @03:14PM (#41184383)

'0.0.0.0' means 'all local host addresses'. Including whatever might be listening on 127.0.0.0/8.

It's just a private network address, and this "vulnerability" is because idiots adhere to the letter of the spec maliciously instead of understanding current practice.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by Titan2189 on Wednesday August 07, 2024 @03:39PM (#41184603)

Wait, so you're suggesting developers shouldn't adhere to specs but instead develop their tools / libraries according to whatever they feel it is the cool kids currently do?

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by rolph on Wednesday August 07, 2024 @04:00PM (#41184789)

i fail to see much difference with:

>>develop their tools / libraries according to whatever they feel it is the cool kids currently do?<<

versus:

>>adhere to the letter of the spec maliciously instead of understanding current practice.<<

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by otabdeveloper4 on Wednesday August 07, 2024 @04:21PM (#41185011)

Yes, I do. You should be following de-facto real world standards, not fantasy ones. Especially if security is involved.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by robertlagrant on Wednesday August 07, 2024 @04:31PM (#41185138)

If there are de facto real world standards, why not write them down?

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by otabdeveloper4 on Wednesday August 07, 2024 @05:23PM (#41185704)

Ask the guys writing the RFC's, not me. Boggles my mind too.

[ Parent | on HN ]

Re:Deprecate 0.0.0.0 for Private Network Access by datanut on Wednesday August 07, 2024 @08:35PM (#41186943)

Have you considered replacing/creating/updating RFCs/BCPs relevant to your field?

[ Parent | on HN ]