Language Selection

English French German Italian Portuguese Spanish

Keepin Ya Posted: SUSE Linux 10.0b3

Filed under
Reviews
SUSE
-s

Well, the hits just keep on coming with the Beta 3 release of OpenSUSE's SUSE Linux 10.0. As with Mandriva's 2006 Beta 3, most of the changes are under the hood. The Changelog is quite extensive and it looks like the OpenSUSE developers have been very very busy.

Upon first login one finds that the nasty "beagle autostarting" bug is now fixed. That's every nice. So much so that I actually had a chance to test drive it. I started it from the menu and had it index my /home folder. From there I searched for "desktop." It found several files and displayed them in a nice browser. Double clicking it opens it in another application. In my case it was kfmclient. Really nice tool with a great look interface afterall.

        

One nice new addition I noticed was this really great menu search tool. At the top of the catagory headings is this box for inputing a term for searching in the menu. Then all the other items fade out except the term for which you were looking - making for easy location and selection. This is a wonderful addition, especially for SUSE Linux due to the fact their menus are chocked so full of applications.

        

That little X lock up glitch from beta 2 is now gone. The developers did quite a bit of work to xorg, but I didn't see anything in the changelog that would apply to my system. Most of their work was on the x86-64 arch, but something fixed it for me.

However not all was perfect. Even though the beagle autostart glitch was cleared up, gnome now insists upon starting up a file manager for each filesystem it finds. I closed them, logged out and logged back in to find, yep, it does it everytime. I even closed them all and click 'saved setup for next login' and retried. I had 15 little filemanager windows open each time.

    

Sound is now enabled at log in and the kde welcome wav greeted me this time. They have given OpenOffice.org a new splash image that looks really nice. Also included are many nice backgrounds for the desktop as well. Some are of a nature motiff featuring animals, fauna or landscapes. Others are SUSE specific. I had the installer install the nvidia drivers and Microsoft fonts during the "check for online updates" this time and that was wonderful. I didn't have to fiddle with anything at all to obtain 3d acceleration. That's a really nice feature. Have I mentioned what a nice kdm background and kde login splash screen is included?

        

Their efforts are evident and obvious as SUSE Linux begins to shape up and really show the polish. The system is fast and quite stable, not only that, it's slick and smooth (other than that gnome thing). I predict unprecedented number of downloads once 10.0 goes gold and SUSE fans will not be disappointed.


Changelog Highlights include:

  • beagle:

    • Disable autostart in KDE and other autostart fixes

    • Remove upstreamed patches
  • hwinfo:
    • fix pppoe detection

    • fix pcmcia probing and controller detection
    • getsysinfo collects a bit more info
    • load lp module
  • gdm:
    • Remove upstreamed autologin patch

    • Now installs .desktop files in correct location
    • Make the default session option work on autologin
  • kernel-update-tool:
    • Initial release.
  • sysvinit:
    • Enable patch for killproc

    • Avoid zombie processes using startpar
    • Add the possibility of using pid numbers instead of a pid file
  • sysconfig:
    • removed logging into a file in /tmp

    • use mktemp for temporary files
    • move static lib and la file to /usr
    • Also change default of USE_SYSLOG to "no"
    • make 'status' work in rcnetwork
    • wireless: added support for WEP keys up to 232 bit when entered as ASCII
  • udev:
    • Removed all occurences of /etc/hotplug/functions from udev scripts

    • Moved isdn.sh and firmware.hotplug.sh to /sbin/udev.*.sh
    • Added README.Logging and a helper script to docdir
  • yast2:
    • added check for `cancel to ncurses menu loop

    • added simple XEN detection & select kernel-xen if XEN is detected
  • MozillaFirefox:
    • added backports (firefox-backports.patch)
    • fixed Gdk-WARNING at startup
    • workaround for linking with pangoxft and pangox

    • remove extensions on deinstallation
    • include dragonegg (kparts) plugin
    • fixed installation of the beagle plugin
    • included lockdownV2
  • kernel-default:
    • update to 2.6.13-rc6-git13-4
    • network, ide, nfs, md fixes

    • lots of alsa and xen updates
    • lots of bugfixes
  • Lots of kde, hal and xorg bug fixes, patches and updates
  • Numerous version updates



More Sceenshots HERE.

The full rpm list is here.

That Pre-Release Software License Agreement is here.

The trimmed Changelog is here.

Please see my report on Beta 2 and it's Screenshots for some history, while my Beta 1 review and it's Screenshots give a good introduction.

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