Language Selection

English French German Italian Portuguese Spanish

Does Longhorn Even Matter?

Filed under
Microsoft

Microsoft’s Jim Allchin is out plugging "Longhorn," even though the OS isn’t expected to be released for more than another year. Apparently, not content to copy features from the Mac OS and Linux, the new MS mantra ("It just works") is also borrowed from Apple’s ad campaigns.

In the Fortune piece, Allchin brags to David Kirkpatrick about Longhorn automatically defragging your hard drive, a practice I’d forgotten about since switching to Linux as my main OS in 1999. He also brags that longhorn will display a preview of a document in the icon, something that already works for many document types in Nautilus (the GNOME file manager) and others. He boasts about new versions of Windows running on 64-bit chips, but Windows is the slow kid in the classroom on that as well — Linux has done 64-bit on x86 chips for years now, and Solaris and Mac OS X (to name just a few) have already beat Windows to the punch there as well.

Charles Cooper points out why Longhorn matters, though not in a good way for Microsoft. Basically, Allchin and company are trying to stall for time. As the world eyes Mac OS X and Linux, Microsoft is trying to keep up the hype until they can push Longhorn out the door. It’s a standard Microsoft tactic — when the competitors are releasing software that does what people want now promise something better later in the hopes of keeping customers onboard. Granted, Microsoft has inertia on its side, so it’s unlikely that Longhorn could be an Itanium-style disaster for Microsoft — but, if Microsoft doesn’t deliver, on time, it will have some negative consequences for the company.

Full story with live links and discussion.

I refuse to be distracted...

Just so I can say this again for the (insert huge number here) time and risk boring just about everyone to death...My bagle attack via our network a while back sealed Microsoft's fate with me and my company. I can't help but chuckle at the similarities between my OS situation and an old girlfriend. I am happy now with Linux, and there is something new every day that excites me about it, but just every now and then, I catch a glimpse of Windows XP, something new or improved and can't help looking it over a bit and remembering the good times. The analogy continues to work when you decide to secretly revisit the old situation in a clandestine meeting...only to eventually re-discover the exact reasons you kicked her to the curb.

I have kicked Microsoft Windows to the curb. My attentions, energies and complete allegiance (if there is such a thing) is to Linux. Linux provided me a safe and reasonably easy alternative when I was in crisis and the people involved in my particular OS of preference, PCLinuxOS, helped me when I most needed it. That's right helios, it's ALL about you now isn't it, your needs; your wants...?

Yep, thats exactly what it's all about and Linux has catered to that. Microsoft left millions of people hanging for weeks and months at a time with unpatched vulnerabilities and unanswered questions about security issues. Issues reported by a handful of companies who keep an eye on that sort of thing, and only when the uproar got loud enough did MS admit the problem and work out a solution. All of the above just to say: I don't care what Microsoft does anymore. Furthermore, I wield my self-proclaimed ambassador-ship at every opporutinity. Not only is Linux becoming a better solution on the server side, Linux is going to mess around and find themselves a viable alternative to XP on the desktop. Now it's up to the developers to make it so.

helios

"Telling a drug addict to just say no is like telling a manic depressive to just cheer up" - Abby Hoffman, God Rest Him

re: I refuse to be distracted...

Wonderful commentary. Security issues were the deciding factor, I'd almost say the primary factor, in my switching to Linux almost 5 years ago as well. You make a very good point mentioning M$' delay in releasing updates and fixes. It's always been so. But what's worse is when they finally do, they can and do break many of the system on which they are applied. It's just unreal. I've been thankful to the Linux community since the beginning. I've never looked back tho. None of the fancy do-dads people write tempt me. To draw upon your analogy, I feel about M$ as the boyfriend who betrayed you again after you forgave him the first time - and I never, never would put myself in that position again. I wouldn't miss it in the least if it just disappeared off the face of the earth. In fact I'd probably rejoice.

Thanks for sharing your wonderful story with us.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers