Language Selection

English French German Italian Portuguese Spanish

grrrrrr-rr4

Filed under
Gentoo
Reviews
-s

In my continuing search to find a binary gentoo installer, one that will install a complete working system in much the same manner as SuSE, Mdv, or PCLOS from a graphical environment that I can then rebuild for my arch/system/requirements at my leisure, I tried RR4-2.65.1 this morning. RR4 is a livedvd "designed to transform a computer into a powerful Gentoo Linux system in less than 5 minutes," according to description provided to DistroWatch.

I've been a loyal gentoo user for little over two years now and have installed per stage 1 about 4 or 5 times. My server on which this site is run is one example. But I've been looking for a graphical environment from which to install gentoo, a way to encourage others to install gentoo without having to read pages and pages of documentation. I've tried several distros/methods lately, and none have yet to equal the functionality I found in Litrix.

The system starts out really impressive. I booted the livedvd and was given the option of just hitting enter or perusing several booting options. Then the silent boot features a lovely splash that utilizes a kde-like progress of highlighting icons rather than a progress bar and all accented by the lovely gentoo purple color scheme. The verbose boot looks just like my everyday gentoo system booting - a variation on the regular linux boot you've all probably seen many many times. A beautiful desktop greets you and lulls you into a sense of confidence. The desktop appears so polished and refined. The menus are chocked full of useful applications and tools. The fonts are great looking and performance is amazing (considering it appears built for i386). It features a 2.6.14-r2 kernel and uses a 6.99 of Xorg. The crowning jewel is the installer. It's the whole point.

        


Yes, it's a mighty fine livedvd and if that's your desire, then they have you covered. I don't recall when I've seen such full menus. But at 2.4 gigs, the iso should be complete. It contains not only KDE 3.4, but also gnome and some other lighter window environments.

However, ...you knew there was going to be a "however" didn't you, however, the installer bombs out here. It's a beautiful piece of software. It features a lovely windec and exquisite widgets. The fonts are gorgeous. Options seem insightful and complete. I was quite impressed. Too bad it don't work.

The installer begins with a graphical configuration which walks one through all the options. Partitioning if needed, naming / partition, networking, type of install, use flags and chost options, root passwd and useradd are just some of the steps. Among the choices for type of system are the standard stage 1, stage 2, stage 3 and install the livedvd. If you chose any of the stages you can choose your USE flags, arch and chost. It defaults to stage 3, but I chose install the livedvd my first attempt, figuring this would be the fastest and easiest. After configuration and clicking "install," the installer outputs root password is setup, then stops. I waited quite a while before checking with top to make sure it wasn't doing anything. I waited some more to make sure even though the hard drive light was still not blinking. Eventually I decided "welp, I guess that didn't work."

        


My second attempt was to use its default of stage 3. I restarted the installer and chose that and proceded to spend about an hour choosing my USE flags, chost and arch. When I clicked on athlon-xp the X server crashed and sent me back to the login. That's when I said, "pffffttt, I ain't trying no more!"

I visited the forum before my first attempt for help in deciding which type of install to use. No real information was found on that topic, but I did see some reports of successful installs, mostly using the "almost gentoo method," and even some posts about destroyed partition tables. No damage was inflicted here, but no system resulted either.

Second thought, I wasn't quite ready to give up yet as it turned out. Upon typing the text for this article, I became aware that I really hate having to state that a distro doesn't work, but I must obey my journalist integrity. So, I decided to give RR4 one more chance. I went through the whole shebang again, spending not quite the same amount of time considering the USE flags. It still just stopped at setting the passwords. I was bummed.

        


So, in the end I'm left to state that the RR4 gentoo-installer is still non-functional. It states clearly on their homepage that rr4 is still alpha so one can't really complain too much. It is impressive at this point and one to keep an eye on. If anyone has a "it works for me" story, I encourage you to please share your comments or, even better, your own blogged review.

So, my quest continues...

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