Language Selection

English French German Italian Portuguese Spanish

Baby did a bad bad thing....

Well from the last thing I wrote in here somewhere (being new means you have no idea where things are), things have changed on the laptop front. After writing some good things about Ubuntu I stumbled across some articles on Suse floating around the 'net and up pops the thought, "perhaps I didn't give it a proper go". Dangerous thought, very dangerous. After some deliberation it was probably a good idea to stick with what I had. So, off to the gym for some torture... erm... exercise. 2 hours later, sat in the bar trying to accumulate some fluids, an apprehensive looking wife says "we need to call at tescos on the way home"... I hate shopping.

Off we trot to tesco and I meander through the magazines section, Ooo, wonder if he'll be any good as bond? Nice tackle... fishing magazines, not that I do. No patience. New rebreather? How could I justify that to the tax man? Anyway, my gaze lands on Linux Format Magazine, hmmm, not seen that before. So I wander around the supermarket, head in the mag, following my wife... could have been anybody's wife. Suse 10.1 plus bits on the free DVD. Ati drivers too. The Ati drivers on my laptop never quite worked properly before (apart from under XP). I'm taking this the distance, to the checkout at once my good woman... well after an hour of browsing just about every aisle in the place.

Home at last, check mail, make tea, stick the madras in the oven and read the mag. The DVD is shinning there, and I'm a magpie. I lost the fight and stuck it into the DVD drive, install the ATI drivers and managed to break Ubuntu. Back to the prompt, X11 xorg copied, reboot and back in. Wonder if Suse would be better? Back into the thought danger zone. Backed up some files to the server (missing the mail file and some other bits DOH!). It's 11:30pm and I started to install Suse. What a good idea that was! 00:30am, still installing and what time do I have to get up? Oh right, that will be 6am then. 01:30am and installed. Don't know if it works, don't care, need sleep. There was a fight this morning with the alarm clock. Why why why can't I leave things alone!?!

Ok, so now I'm up, at work and struggling, this klix coffee would strip paint faster than brake fluid and I'm drinking pints of it, it's easier to write this than debug some of this PL/SQL. I brought in old faithful too and we have a lack of power outputs here and something about HSE and wires across office floors? Silly rule!. Suse is up and running again, on the main laptop this time (faster and newer than the one I tried it on last time). But.... it's a marvel chipset Netgear wireless and Suse no likey likey, connect to the internet it says, download something to fix it... hmmm, I'd like to see that one, no hard wires here, no phone sockets either, and to top it all off, I can't find my usb memory thing. Bugger. I wonder if the ati is recognised in 3D mode thing? Ah, direct = no. Isn't this where I was with Ubuntu only way behind? Click click click, and into some Yast configuration thing. Reboot and lo and behold, Direct = Yes, glxgear throwing out good performance. Still no network.

The laptop is a pentium IV, 2.5ghz, gig of ram (128 shared with ati), 60gb hard disk. It wasn't sluggish and ran XP quickly (when first installed, add the spyware, bugware, wifeware and that did bring it down a little) but it seems to run a tad sluggish with Suse, it wasn't exactly going to win speed awards with Ubuntu either but I heard somewhere that you can tweak this thing more than Ubuntu? It seems to take an age to open anything, nice splash screens though. Have I done a bad thing installing this? I guess it's a wait and see but I don't give up easily... I'll get it working by hook or crook, any tips for adding a nitros kit are very welcome! Oh, at the request of her that must be obeyed, it's running gnome not kde (can you install both and run one for one user and tuther for tuther?) Suse looks nice though, if only I had some dilithium crystals, a phaser and sonic screwdriver. We have ne power Jim!

It's all my wife's fault, I was happy Ubuntuing in Ubuntu ignorance before we went shopping... I hate shopping.

More in Tux Machines

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

today's howtos