The proxy sits on your local net and interfaces to the public infrastructure, so MITM is a non-issue, besides you certainly weren't protected from that at all before so it's wired to be bringing it up as a possible drawback now.
I'm not going to do all your homework but you can start here. I hate posting links from a phone which is all I have to post with at the moment, but this should give you reason to suspect I might know about this issue enough for you to want to research it for yourself.
That is not correct. All ICANN assigned TILes are for public hostnames, and should never resolve to hosts in the private IP range. You violate the standard at your own peril.
There is nothing wrong with connecting to the internet and then violating the standard? Ok. When you do that there is nothing wrong with getting bit by your own stupidity either. The.com and.dev TLDs are controlled by ICANN, who issues them and ties them to a public IP address. If you then fuck up your internal DNS, that's on you chumley.
No it isn't, because those servers don't have a domain name ending in.dev, as that is an ICANN assigned TLD. This is what you aren't grasping. It is like you are labeling all the rooms in your house with street addresses and then complaining that the post office keeps delivering letters to another house instead of your living room or kitchen.
I'm saying that as standards evolve we are all required to adapt. Nobody needed to "monitor the internet" on this one. It was widely announced and Slashdot has covered it many times. If you don't have anyone in your company who keeps up on current events in the industry that is on your company, not the industry.
At least I finally figured out *WHY* you have been saying all these ridiculous things. Newsflash, there is no *client* certificate in an HTTPS transaction. All these conspiracy theories you have concocted are based on a fundamental ignorance of HTTPS and how it works.
And if *you* understood you would know.dev is a valid ICANN assigned TOLD not available for your internal use. You don't get to violate standards and then cry foul because the rest of the world follows them.
HTTPS adds nothing to the ability of endpoints to identify you. They can already do that just fine, and the client negotiates a unique key per transaction, so your apparent belief that there is some master key that acts as a global identifying fingerprint stems from complete ignorance of how TLS works.
Right, but minor correction. The dev TLD is an ICANN issued TLD, so this has nothing to do with local / intranet traffic. Just as you should not use.com for internal machines you should not use.dev or you are violating standards.
I really never thought I'd never see the day when Slashdot would deteriorate so far that your posts on this subject wouldn't be nodded down to oblivion immediately. Do you even really believe the bullshit you are spewing in this thread or are you trolling?
Slashdot Mirror
That's correct.
The proxy sits on your local net and interfaces to the public infrastructure, so MITM is a non-issue, besides you certainly weren't protected from that at all before so it's wired to be bringing it up as a possible drawback now.
You are a fucking idiot.
Standards provide the definition dumbfuck.
I'm not going to do all your homework but you can start here. I hate posting links from a phone which is all I have to post with at the moment, but this should give you reason to suspect I might know about this issue enough for you to want to research it for yourself.
No, that is not the topic, because by definition those servers do not end in .dev. That's the part you don't seem to be able to grasp.
Set up self signed certificates for use internally. That's why God created them. :^)
That is not correct. All ICANN assigned TILes are for public hostnames, and should never resolve to hosts in the private IP range. You violate the standard at your own peril.
There is nothing wrong with connecting to the internet and then violating the standard? Ok. When you do that there is nothing wrong with getting bit by your own stupidity either. The .com and .dev TLDs are controlled by ICANN, who issues them and ties them to a public IP address. If you then fuck up your internal DNS, that's on you chumley.
No it isn't, because those servers don't have a domain name ending in .dev, as that is an ICANN assigned TLD. This is what you aren't grasping. It is like you are labeling all the rooms in your house with street addresses and then complaining that the post office keeps delivering letters to another house instead of your living room or kitchen.
Your sandbox is filled with faux sand. I'm sorry you are not standards compliant, but that isn't Google's fault now is it?
So this is a non-issue for those servers then, isn't it?
I'm saying that as standards evolve we are all required to adapt. Nobody needed to "monitor the internet" on this one. It was widely announced and Slashdot has covered it many times. If you don't have anyone in your company who keeps up on current events in the industry that is on your company, not the industry.
This has literally nothing to do with Network Neutrality, *except* that HTTPS makes violating it more difficult.
At least I finally figured out *WHY* you have been saying all these ridiculous things. Newsflash, there is no *client* certificate in an HTTPS transaction. All these conspiracy theories you have concocted are based on a fundamental ignorance of HTTPS and how it works.
That's bad advice. .test implies it is a test server, not a development server.
It is very easy to setup up automatic renewal.
Use a proxy.
No. You don't.
And if *you* understood you would know .dev is a valid ICANN assigned TOLD not available for your internal use. You don't get to violate standards and then cry foul because the rest of the world follows them.
HTTPS adds nothing to the ability of endpoints to identify you. They can already do that just fine, and the client negotiates a unique key per transaction, so your apparent belief that there is some master key that acts as a global identifying fingerprint stems from complete ignorance of how TLS works.
That is the weakest troll I have seen in a long time, unless you believe that, in which case you are an idiot.
Right, but minor correction. The dev TLD is an ICANN issued TLD, so this has nothing to do with local / intranet traffic. Just as you should not use .com for internal machines you should not use .dev or you are violating standards.
I really never thought I'd never see the day when Slashdot would deteriorate so far that your posts on this subject wouldn't be nodded down to oblivion immediately. Do you even really believe the bullshit you are spewing in this thread or are you trolling?
Someone should invent proxies.