![]() PS: It's a pity, because your product is great. I am sure my company is not the only one. My company (>20k staff) is currently doing an IT assessment and will discontinue all proprietary code with Russian ties. As long as you have ties to Russia, there is nothing you can do to prevent Russian authorities to demand access to the proprietary parts of your code with nefarious intentions, and there is no guarantee you can give for buyers in the west to trust you. ![]() I understand that you personally did not start the war (or even support it), but if you want your company to continue making business in the west, you need to take this seriously and act decisively now. This is not a "situation" that one "does not like" or wishes to "end soon".This is a genocidal assault on an independent nation by an out of control aggressor.Make a clear statement, present a clear plan to cut all ties to Russia (the next North Korea) or else good luck with your business in the west. I am sorry, but this lukewarm statement dances around all the wrong bushes. We'd prefer to avoid making users uncomfortable. ![]() The problem is that it will break cosmetic rules for all AdGuard users until they restart protection. So in theory we could change it right now. On the level where AdGuard works there are no domain names, there are only IP addresses.Īctually, AdGuard itself resolves this domain before starting protection and uses the IP returned by the DNS server. I assume that you should intercept the domain name. It is very easy to trigger people these days. Second, some DNS servers may consider it a DNS rebinding attack and reject it.Īlso, why do you need to change the hardcoded IP next release? First, there's a slight chance of intersecting with a real intranet IP and breaking access to it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |