Language Selection

English French German Italian Portuguese Spanish

An Arabian Night

Filed under
Linux
Reviews
-s

Arabian Linux 0.6 beta 4 was released on or about September 4, and at the request of a reader, Tuxmachines downloaded, burnt and test drove this lovely installable livecd tonight. As the name implies Arabian is primarily designed for Arabian speaking users, however it does have support for English as well. Since this latest release is two month old, some of the packages are going to seem a big dated, but it none the less is worth a look. Great looks, stability, and imaginative customizations make Arabian a worthy contender in either language. In fact, Tuxmachines was quite impressed.

Some of its notable features include:
* Arabian Language support in Gui and consoles/logs/configuration tools etc
* winmodem support
* hard drive installable
* Based on Debian and Kurumin (which is based on Knoppix)
* accurate hardware detection

Features of 0.6 beta 4 include:
*Kernel 2.6.11,
*Xorg 6.8.2
*Gcc 3.3.5
*Using LSB color system,
*Interactive bootup system,
*KDE 3.4.2 (local compile)
*Automount for cdroms & desktop icons
*OpenOffice.org 2.0 Beta 1
*Java 1.5 enabled as default
*Partitions and virtual directories rw
*Enhanced support for wireless cards
*Added Kernel Accelerator - kqemu for qemu

Upon boot one is given the choices of (1) Arabic Language, (2) English Language, (3) Extra Hardware Detection. It's a pretty yet professional quality boot screen featuring easy editing of the grub system booting options. The splash option didn't seem to do anything as the splash=silent booted using the same =verbose screen. But as the initial boot screen, the background splash is subtle and unobtrusive.

    

The default desktop is quite attractive in itself with a lovely lavender based wallpaper and an Arabian-looking symbol or letter as the focal point. Utilizing kbfx to dress up the panel elevates the desktop to a more classy level. But when enabling super karamba, one get a whole different look and feel. I like the defaults they set up and it makes for a really nice looking desktop with popular applications already set up on the launcher.

    

As stated above, it comes with kde 3.4.2 and many of the usual kde applications including the kde control center. They also added other thoughtful apps like mplayer, firefox/thunderbird, synaptic, and OpenOffice. But Arabian has a nice set of their own tools for many tedious tasks.

        

A pair of these is the apt-manager and the deb-manager. They appear to be complimentary applications for the installation and removal of software packages. The apt-manager appears to be used for setting up your chosen repositories and deb-manager is the actual installer. They are simple yet attractive looking applications for handling the task if one wanted an alternative to synaptic or using apt-get at the command line.

    

In the menu one can find many useful additions to the usual kde fair. For example the Daily Menu contains kde items that one might find commonly used, however, in System are links to applications to enable/disable sudo and karamba as well as the configuration or enable/disable of several server applications. Under Utilities one can find shortcuts to installing software classified by purpose such as compilers/programming or internet, P2P, email. Also under Utilities is where all those Arabian-Scripts are found such as the apt-manager and deb-manager spoke of earlier as well as many others. I particularly liked the clean uncluttered appearance of Arabians gui tools.

        

However, the piece de resistance is the Arabian Control Panel. Like the apt/deb managers, it's gives an understated appearance, yet looks can be deceiving. Under the simplistic facade lies many useful tools for configuring your Arabian Linux system. From this one "panel" one can configure just about anything on their system from hardware/peripherals settings to network settings including a firewall or wireless adapters/access points. Also included in the menu and in the Arabian Control Panel are links/apps to configure many software driver dependent modems (aka winmodems).

        

The crowning jewel of the Arabian Control Panel is the hard drive installer. Another piece of original software presented in the now familiar Arabian understated gui fashion awaits to walk the user through an easy hard drive install. Just a easy few steps, perhaps 6 or 8, is all that is required to set up your hard drive install for your system.

        

        

In conclusion, tuxmachines found Arabian to be a very nice Linux system for a newcomer or even an experience user. It seemed quite stable and all the Arabian tools functioned smoothly. The system as a whole offered a different look without taking customizations to an extreme. It comes with many nice applications and plugins with quite a few extras. I liked it quite a bit and can recommend it to anyone without hesitation. You may visit the very nice Arabian website here for further information. More screenshots in the gallery.

        

Arabian Beauty

Thank you for taking my suggestion to review this distro.
It's really an Arabian Beauty Smile
Nice review for a nice distro.

Simply Beautiful

That is so elegant looking. Very nicely done.

re: beautiful

Yeah, it is nice. It has a real stable solid feel to it as well.

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

English forum

Unfortunately, the English forums is not available anymore in their website....

re: English forum

Oh yeah, I noticed that too, but didn't think to mention it in the article. Bummer huh? Sad

----
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

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