Language Selection

English French German Italian Portuguese Spanish

Mandriva 2006 Final Look

Filed under
MDV
Reviews
-s

As you know Mandriva 2006.0 was released to club members on October 6, and then it was released to the general public yesterday, October 13. It is available at the time of this writing only as an ftp install. No word at this time of when isos will be made public but if you can download an iso, then you can do an ftp install. In fact, I prefer ftp installs in a way because you only have to download the packages you actually need. In addition, when you define a mirror for your ftp install, the information is usually stored for later and continued use through urpmi. In addition one doesn't need to waste more cdrs to have to dispose of later. Ftp is the way to go.

As we followed Mandriva through the 2006.0 development cycle we found many new features and vast improvements in other areas. Today we summarize the operating system that Mandriva 2006 has become.

Installation

So, pick a mirror and navigate to the official/2006.0/your_arch/install/images directory and download the boot.iso or network.img. The boot.iso is a 12.5mb iso to be burnt onto a cdrom while the network.img is a 1.4mb image to be dd'd onto a floppy disk. Both are used to boot your machine and start the install. If you prefer to use the floppy disk method, you may wish to read the readme as you may need additional disks such as for uncommon device drivers or the like. Note your mirror path to the arch directory. Upon boot of the boot.iso you are presented with a menu asking what type of install you'd like to do and in this case choose ftp install. After configuration of your internet connection, you can either use one of their predefined categories of mirror types or choose define your own. I'd suggest you have a mirror backup written down in case the mandrake predefined mirrors don't work out. I usually choose list your own and fill in the information. Then the install goes as usual. Pick your language, type of install, where to install if necessary, partition work if necessary. Then you choose your package groups or individual packages if desired and wait. If it's a network install, this will take more time than you might be accustomed to. After the packages are installed you are given the opportunity to set up users and passwords, configure your hardware and system, and setup a boot loader. Then you can boot into your shiny new Mandriva 2006 desktop.

Features:

  • KDE 3.4.2

  • Gnome 2.10.2
  • Kernel 2.6.12.11
  • Xorg 6.9 (cvs20050915)
  • Kat 0.6.3-19
  • Firefox 1.0.6
  • Gaim 1.5.0
  • OpenOffice.org 1.1.5
  • Nvu 1.0
  • Gcc 4.0.1
  • Evolution 2.2.3
  • Xine 1.1.0
  • Gimp 2.2.8
  • Interactive firewall
  • Full integration of Skype
  • Integration of Conectiva's and Lycoris's technologies
  • Official support for the Intel Centrino mobile technology
  • Full RPMlist as tested

The first and most noticably striking improvement is Mandriva's new blue penguin theme. A wonderfully tasteful choice after the 2005 Monster Tux. I'm not sure if it was ruined by the use of the new Disco Duck start up wav or not. j/k The new theme runs throughout Mandriva 2006 sporting pretty graphics, interesting sounds and colorful icons everywhere. Mandriva has become absolutely beautiful.

        

        

New this release is the Kat Desktop Search tool, which was covered fairly well in my Beta 2 report or my RC1 report. Kat is a desktop search engine that can index a directory or your whole system for comprehensive searching. Results can be as extensive as you define. A wonderful tool written by a really nice guy.

    

Also new in 2006 is the Smart package manager. Smart is different from other package managers in that it can use different types of packages, other than what the system specifically uses. It has configurations available for urpmi repository, rpm directory, apt-get repos, apt-rpm repos, Slackware repos, deb directories. This topic too was covered in more detail in my RC1 report. I'm not sure of the fate of Smart in Mandriva as I heard the developer has since moved on. Have no fear, for Mandriva's original package manager is still intact and performing to near perfection either by commandline or graphical interface.

        

And of course, Mandriva wouldn't be Mandriva without their famous Mandriva Control Center. From this one application one finds modules to configure their entire system, from network connection to firewall rules, from software installation/uninstalls to distribution upgrades, and from booting/startup options to hardware configuration. It is their flagship application where you can do all these thing and so much more.

        

Conclusion

All in all, as I've followed the development of Mandriva 2006, one thing has become clear. Mandriva is ever improving and it is reflected in this new more polished stable operating system. Featured here is only a taste. Throughout the entire development cycle I experienced very few applications crashes and never a major X server crash or system lock up. The compromises between bleeding-edge and stable applications has paid off tremendously for Mandriva. I've found the upgrade process perfected to a dream and the installer remains one of the key features that drives Mandriva's popularity. In this release not only is the look and feel improved, they have introduced new technologies and features for the novice and experienced alike. Mandriva provides enterprise level software and support as well as a free-for-download version and support in the form of mailing lists and forums. There are also unsponsored newsgroups, forums, and irc channels. To me, Mandriva is a world class system that can meet any user's needs, as it comes with just about any application in existence and many server applications as well.

Mandriva, the people's Linux.

All Tuxmachine's Mandriva coverage can be found HERE.

Mandriva's own Press Release is chocked full of further information.

Changelog since RC2:

  • Fixes
    • mozilla-firefox-1.0.6-15mdk: Security update, synched with FF 1.0.7
    • cvs-1.11.19-6mdk: security fix for cvsbug
    • desktop-common-data-2006-2mdk: Fix desktop-directory script
    • kat-0.6.3-19mdk
      • use html2text -nobs
      • fix search on multiple words (Laurent)
      • default wait time to 20 seconds
      • fix clearing of result windows (Laurent)
      • fix exclude dirs (Laurent)
      • more debug filtering
      • fix fulltext_eml
    • gnome-panel-2.10.2-10mdk: fix for UTF8 encoded url in .desktop file
    • libgnomeui2-2.10.1-10mdk: read UTF-8 encoded url in .desktop file correctly
    • kdebase-3.4.2-55mdk: various cosmetic fixes
  • DrakX 1.1092 / drakxtools-10.3-0.64mdk
    • Bootloader: cleanup sanitize_ver(), makes label longer but cleaner
    • Drakfont (interactive_mode) fix layout (license_msg) merge 2 similar strings
    • Keyboard: added "fo" keyboard, synchronized XKB keyboard names with what is in latest xorg
    • Network:
      • set hostname only after packages have been installed, or else graphical urpmi may fail
      • fix dvb crash during install
      • show IFW button even if not connected (#18708)
      • don't try to connect auto-magically ethernet interfaces during configuration in install, restart ethernet interface for pppoe connections, add some reminders, fix indentation.
      • use mandriva.com for connection tests
      • fix crash (ugtk2 dialog helpers aren't imported)
      • force menu refresh when interface status is modified (#18636)
      • pppoe_modem device doesn't exist, automatically configure DSL connection on installation from DSL
      • net_applet: fix crash when only one interface is configured
      • (is_ifplugd_blacklisted) do not blacklist anymore b44 since it now support reporting link status according to Arnaud Monnet de Lorbeau
      • restart hsf/hcfpci services when needed support madwifi drivers
      • increase timeout after a wireless network is selected don't vivify hash ref
      • allow to up/down any network interface (backport of my 2005 patch for PSA)
      • better handling of ASCII WEP keys (partial fix for #18558)
      • don't try to update shorewall configuration if it's disabled drakconnect: update interfaces list in shorewall drakconnect: write wireless settings in wireless.d/ as well
      • read shorewall net interface from configuration file first
      • lower signal level given by wpa_supplicant fix hidden ssid always recognized as current when using iwlist fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • net_applet: refresh wireless networks every minute only fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
      • don't resize state icons show refresh icon if network isn't connected show ESSID if already configured for hidden ssid move signal strength icon on the left don't automatically refresh networks list use Managed mode if AP isn't Ad-Hoc drakconnect: write wireless settings in wireless.d/ as well fallback to wpa_cli or iwlist/iwconfig when needed (#18516)
    • Packages:
      • don't warn lisa (which is installed by default)
      • more x86_64 mirrors (works, tested as lftp $url -e exit)
    • Hardware
      • ugly hack: wait for usb-storage devices to appear (bugzilla #13395)
      • display cards that offer additional parallel port in the system class rather than in the "unknown" section (custom_id) try harder to have a sane name: before fallbacking to the class name (eg: "Printer"), try to use the vendor name (eg for printers)
    • comment/dis-comment the content of ld.so.conf.d/{nvidia,ati}.conf instead of symlinking to a hidden file (implies the new ati/nvidia packages have config(noreplace) for those files) instead of symlinking, comment the content of the ld.so.conf.d/*.conf don't load glx with fbdev (since glx is used for various things nowadays, dixit fredl)
    • Printer:
      • Do not auto-install "sane-frontends" for MF devices.
      • On USB printer hot-plugging sometimes parallel printers are also shown in the window popping up to ask whether the printer should be set up. Even sometimes parallel printers which are not connected or turned on any more were shown. Fixed.
      • Adapted file names to check for to the changes on the HPIJ 0.91-8mdkpackages.
    • filesystem:
      • increase /usr max size
      • fix typo during install, don't use half working dmraids (#18386)
    • Drakbackup: Remove unclear text (not needed, #18619)
    • Upgrade
      • we do want doPartitionDisks and formatPartitions to be done early on upgrade, so that selectKeyboard is done when the partitions are mounted
      • call set_all_default() (to fix fstab on upgrade) before install packages so that {useSupermount} is correctly set (maybe we could also move the set_all_default on install there) since choosing keyboard is done after mounting partition to upgrade,
      • ensure we have gnome-volume-manager when we have gnome or kde (to handle cdrom auto mounting)


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