Re: Won't be used in upcoming builds..
check out dnsdist by powerdns. high availability proxy for dns that answers dns over https queries. use that in combination with their recursive dns server. done.
239 posts • joined 4 Sep 2009
Whatever they say about a military aircraft, it's not entirely accurate. An F-15 is rated a mach 2.5. An F-14 was rated at machine 2.3+. In reality, the F-14 was faster than the F-15, but the F-15 had faster accleration. The F-14 would climb to 56K ft. Like it was nothing. Getting to 60 or 6th was not hard. If you want to fly over much 2, those are the altitudes you need to be at.
Someone got phished. This is how it starts. This is how they get a toehold. We used a system whereby we external snapshots on a device that could spin up any of the snapshots as a virtual machine. The system also kept those snapshots on a private cloud and could be spun up from there as well. Wi Dows has enough vulnerabilities that once on a machine, that's all it needs.
Even Firefox is putting in DNS over https, but you can disable it or change where it sends queries.
Punting chrome and chromium
They've already made all that money back in profits. A lawsuit like this needs to extract real pain from a company. This will change nothing about Google's hiring practices. I'm over 40. I go for an interview. Inquire after the interview. "Another person was a better fit." That's all they have to say. The victim has to prove the offense. The words used keep the employer from being sued. The penalty should have been 111 Million or even a billion dollars. Meanwhile, Google claims a shortage of engineers and goes for H1B people. It's BS.
I'm over 40. I've been dealing with age discrimination for the last 20 years.
I agree as well. When I first underwent certification training for line of equipment, I was given the rule of thumb; the higher the frequency, the more it acts like light. at the time we were talking 2.4 and 5.8 and that 5.8 would give near line of site, because it would reflect off of things while 2.4 was a lower frequency and it needed line of site. Also part of that rule of thumb is that the signals wouldn't penetrate solid water. A rainstorm is solid water as is a tree. 24 GHz would be good for setting up short hop meshes which, I think, is the idea.
We're talking about a company owned, essentially, by the communist party in China according to this article: https://www.nytimes.com/2019/04/25/technology/who-owns-huawei.html
Its ownership is rather murky, but the point is that all Chinese companies are required to assist the Chinese government in intelligence operations. read: spying. What is to stop Hawei from building a backdoor into the operating system for the core switches they produce allowing all communications across that switch to be monitored or worse, permanently disable that switch thereby ceasing all communications for that switch? Now replicate that across all of the switching offices that contain Huawei equipment and your country's telecommunications are dead with no recovery but replacement. Call me paranoid, but I'd rather not take that chance with the security of my country with hardware/software from a country that is not exactly my friend and clearly belligerent in some cases.
Asimov's 3 laws as far as robots go. Artificial Intelligence isn't intelligent, yet. It's ok at pattern recognition, but that's bayesian math. decisions still have to be programmed in by someone intelligent.
still, though, machines should not be killing people, ever.
I'm not ready to pay $750 for the cheap version of a phone that's not all that great at making phone calls. I haven't seen anything in them justify the huge price jumps.Tempted to just purchase a new battery and a new back. That's $22.00 plus shipping. There's certainly nothing in the phones that make them stand out from the previous 3 iterations of it.
What could possibly go wrong? This is a security problem, especially if the libraries included with the package are out of date, or worse, hacked. This is a solution looking for a problem and it creates a raft more. Even worse, it's another example of trying add in yet another layer to kill performance.
Yeah, $1,000 is too much for a phone. Smartphones are good for a lot of things, but making phone calls isn't one of them. With 5G coming, it looks like I'm going to get a battery and a new back for it and wait. It's working "ok" for now. Not great, but ok. It was never great and the latest and greatest is certainly not worth $1,000.00
I have two solutions in place. I have a windows machine running virtualbox. commandline, folder sharing, gui, etc. I've been using it for years. so to multipass...yawn. The second solution is a small machine that is running Ubuntu 18.04 LTS with KVM installed. I have Windows installed in a virtual machine for whatever I might need out of Windows. None of my old copies of Office will activate any longer, but OpenOffice and LibreOffice fill that void along with Thunderbird for email. I'm not in want. I have an app for my Canon DSLR which will only run on Windows or Mac so that's why the virtual. The only thing that doesn't work on Linux is Spectrum''s flash app that it uses for it's streaming service. I'm not missing anything there.
If you're using Google's browser, they're getting your search data. You don't honestly think the browser is not sending your search data to Google do you? and what about DNS or HTTPS? Not only do they get your search data, they're going to get all your DNS data, too. You don't thing Google or Cloudflare are offering free public DNS for nothing do you? I won't even get into the fact that both of those services don't update when they should and have very high latency. Soon Google won't allow you to override the dns over https settings. I don't have any trouble with Firefox, though they signed on the the DNS or HTTPS, too. You can disable it. I run my own resolvers locally.
I have never been able to understand why the ad blockers ever blocked anything rather than redirecting the content to /dev/null. That way the upstream never knows if the ad gets shown or not. Then Google wouldn't be trying so hard to force feed us ads. Look for people to start running ad-blocking proxies. Yet another layer.
This is about control and making it easier for corporate and government tracking and getting records for DNS searches without actually raiding someone's machine. Nothing more. DNS over TLS is already defined and solves the problem. Thankfully, there are coming implementations of DNS resolvers other than Google's or Cloudflare's that will do this and changing your browser to user your own or a public one other than Google's or Cloudflare's. Call me paranoid, but I don't trust either company no matter what they say publicly.
The solution is trying to solve a problem that doesn't exist. Moreover, Google and Cloudflare are going to send out normal un-encrypted udp requests to the root servers and then to the authoritative servers for any domain, then encrypt and return the results. the HTTPS protocol is slow and now we'll have yet another layer to add more latency.
Google and Cloudflare want your dns traffic. That's what this is about. A one stop shop to see what you're looking at and to send you a more targeted set of ads and propaganda. If you don't think that traffic won't be logged, I have a bridge I'd like to sell you in ... They are going to dcrypt that traffic and make normal DNS requests to authoritative DNS servers scattered throughout the world. This solves _nothing_. Google's DNS resolvers are slow and don't take updates very well, either. I've had them return incorrect information for hours even days after the TTL on a record had expired. I run my own hosting servers. The have TLS enabled and they can take requests over TCP. The main security problem that is not liked is that DNS traffic uses UDP and not TCP. UDP can be faked easily. simply moving to a TCP based model instead of a UDP based model. As Paul Vixie said, this problem has already been solved. It's up to each OS vendor's resolver to use the more secure protocol if it's available. At any rate, it's going to slow DNS to a crawl.
He was a better fit. It was between you and him. It was tough decision. Have you ever heard that? That's age discrimination. They said all the fright words to say it wasn't age discrimination. I'm 61 years old. I lost count of how many times I've heard that one.
Lately all I can get is helpdesk which pays squat and requires all sorts of knowledge. blecch. I've gone from CTO to peon in 20 years.
Not actually. What I really wish that I'd done was gone to school for something like heavy equipment repair. Those folks are always in demand. Now I'm an unemployed IT worker only a few years from retirement who probably won't be able to land anything but a helpdesk job or something in retail because I'm over 50
Biting the hand that feeds IT © 1998–2020