Language Selection

English French German Italian Portuguese Spanish


some leftovers:

Filed under
  • Precise Puppy 5.7.1 review – small and swift
  • Impressions after the GUADEC 2013 in Brno
  • The Humble Origin (EA) Bundle...Wait...What?!
  • Steam Has Greenlit More Games With Linux Support!
  • Tropico 5 City Builder Will Come To Linux
  • Planetary Annihilation Live Stream 14th August
  • Football Manager 2014 will be on Linux
  • Penguin Evolution Turns Glacial
  • KWin enters the world of QtQuick 2
  • Raspberry Fly? for drones
  • Do One Thing & Do It Well: Ubuntu Needs More Purposeful Apps
  • GNOME Display Settings Now Working On Wayland
  • The Humble Weekly Sale: Introversion
  • Fedora 20 will not install sendmail by default
  • openSUSE Conference 2013
  • Lumail binaries are wheezy only for the moment
  • open source education tools
  • Steam Cards: How Do They Work?
  • Free software for free markets
  • Natural Selection 2 FPS/RTS Will Release On Linux August 30th
  • Check PiCE, a rain resistant case for Raspberry Pi
  • Puppy Linux 5.6 Starts Playing With F2FS
  • GUADEC 2013 Talks Available to View Online
  • Nemoshell: Another Wayland Window Manager
  • Porting KReversi to QML
  • Canonical Is Shutting Down Ubuntu Friendly
  • Archive Managers Compared: Ark vs. File Roller
  • New stable release Marble 1.6
  • FLOSS Weekly 261
  • Flock the First in Charleston
  • Flock 2013 report
  • The sweet, sweet smell of victory
  • Flock 2013 Con Report

some leftovers:

Filed under
  • Linux Graphics News
  • Full circle mag Inkscape Special Edition Volume 01
  • New Study Shows Linux Firmly Entrenched in the Enterprise
  • 7 Linux hwclock Command Examples to Set Hardware Clock Date Time
  • Fedora Linux Set to Build Agile Core
  • How to scan network with Nmap GUI
  • System Shock 2 Cult Classic Sci-fi Horror FPS-RPG Looks Like It Is Heading To Linux
  • Linux Rebooting Refresh
  • Internet Advertising Bureau Turns to Full-Page Ads in Mozilla Kerfuffle
  • Hawaii Wayland/Weston Shell Gets New Release
  • Linux Malware: Should we be afraid?
  • Post open source software, licensing and GitHub
  • How to Produce Vector EPS with CMYK Color Using Free Software
  • grive: Sync with Google Drive
  • Developers: Give us sane and sensible default system and application settings
  • oSC13 – some more details and thoughts

some leftovers:

Filed under
  • Metro: Last Light Looks Like It May Be Heading To Linux
  • Burning Circle Episode 126
  • ERROR: No configuration file found when booting Ubuntu 13.04 using USB stick
  • openSUSE 13.1 Milestone 4, GNOME live ISO
  • Fg/Bg Command – Linux Manage Process Foreground / Background
  • Muscle Car Online A Free Racing Game On Linux
  • diary: Almost functional
  • Open-Source Apache Web Server Hits Ignominious Milestone
  • GNOME's Evolution 3.8.5 Arrives with Lots of Fixes
  • Manjaro Openbox on a 7-year old Acer Aspire 5500Z Part 1
  • Communication in the Post-PRISM World
  • Vim 7.4 Famous Text Editor Released with More than a Thousand Patches
  • Flock day 3
  • python bytecode: classes
  • usevim: Script Roundup: Bbye, Enhanced JavaScript Syntax
  • Best Articles That Review Lightweight Web Browser Midori

some leftovers:

Filed under
  • KDEConnect improvements
  • elementary OS Luna says Hello World
  • The Road to Luna
  • Fedora Flock Recap: Day 2
  • Fedora Flock Recap: Day 3
  • TLWIR: Developing a GNU/Linux-Based Quality Assurance System
  • things i would want to know about erlang
  • Lumail now uses GMime
  • The Performance Impact Of Fedora 19 Updates
  • Convert .flv to .swf in Linux
  • The Linux malware story comes around, again
  • Skrooge Financial Management Software for KDE
  • dmesg: An old, new, cool tool
  • Fedora Badges
  • X.Org 7.8 Isn't Actively Being Pursued
  • Another Great Ubuntu Flavor Linux Lite 1.0.6 Released
  • Plasma Media Center 1.1 RC Release
  • Flock day 2, day 3
  • Easy Linux Remote Desktop | LAS s28e03

some leftovers:

Filed under
  • How to install Raspbian on Raspberry Pi from a USB stick
  • Kernel Driver Not Installed (Rc=-1908) On OpenSUSE 12.3
  • When to add a platform-specific quirk to a Linux driver
  • Martin Graesslin: FLOSS after Prism 2: Anonymity by default
  • Fedora Flock Recap: Day 1
  • Those unexpected regressions...
  • Flock day 1
  • Remotely control your Raspberry Pi
  • gNewSense 3.0 released
  • Finland's Upper Secondary School Exams Going All-Linux
  • OpenSSH Time Brute Force
  • gt5: An unusual disk usage monitor
  • Debian Virtualization: LXC Application Containers
  • Quiz – 15 Linux Basic Questions Part -1
  • Krita Lime (2.8prealpha). New features overview

some leftovers:

Filed under
  • Open source gets its own crowd-funding site, with bounties included
  • Is it too late for new platforms in the U.S.?
  • Gorgeous bug-based adventure game Morphopolis enters alpha today
  • 20 Years of Debian GNU/Linux
  • The Cheapskate's Corner 13 (Aug 9th-15th)
  • Season of KDE 2013 Applications Open
  • Electronic Super Joy
  • FreeNAS 9.1 Screenshots, and Some Suggestions
  • Perl Testing with Test::More
  • LibreOffice 4.1.1 RC1 Arrives with New Features
  • How to version control /etc directory in Linux
  • Open Line on GitHub
  • using nvidia graphic drivers with optimus support got easier with nvidia-prime
  • Monitor Statistics Of OpenSUSE Systems With Saidar
  • gnubg: A better player than I ever will be
  • How to install MariaDB on debian 7 (Wheezy)
  • Automatic image imports with WebHooks
  • Linux 3.11 Power Consumption Results Are Mixed
  • inverto - first person shooter-puzzler with gravity manipulations
  • Accessing the Raspberry Pi’s 1MHz timer, via kernel driver
  • The guys that fight dodgy megacorps and surveillance-happy governments

some leftovers:

Filed under
  • John Carmack leaves id Software for Oculus
  • LinCity-NG for Linux vs. SimCity: Is Free Always Better?
  • Is Saint’s Row Coming To Linux?
  • Aussie Developed Cubemen 2 to be the First Wii U Game with Cross-platform Multiplayer
  • A Nepomuk Integration Plugin for Konqueror
  • Final Term: A terminal emulator to rule them all
  • Drupal 7.23 released
  • Colours within screens within screens
  • GNOME 2 Fork MATE Desktop Aims For Wayland
  • Mir Now Supports VT Switching
  • Best Articles for Command Line Web Browser Lynx
  • create a secure incremental offsite backup in Linux with Duplicity
  • comparison of open source software development and co-creation in digital games
  • Don’t panic: the state of Xubuntu and Mir
  • Linux desktop Trojan 'Hand of Thief' steals in
  • Mitigating DDoS Attacks
  • Fort Disco: The new brute-force botnet
  • Chroot Jail
  • Bring back the BIOS
  • Google: More patents in the service of open source
  • FLOSS after Prism: Privacy by Default
  • How open source is your business / team / developer?
  • Muni LED Sign at Home with Raspberry Pi
  • FLOSS Weekly 260
  • Tuxradar Podcast Season 5 Episode 14
  • TLLTS Episode 517 Aug 7

some leftovers:

Filed under
  • Windows to Linux Migration – Necessary
  • 60 Commands of Linux
  • Open-Source Apache Flex Finally Comes to Linux
  • First Look at Pear OS 8's Welcome Screen
  • Managing Your Own Open Source Efforts
  • Remote Desktop from a Linux client machine
  • Open source gets its own crowd-funding site, with bounties included
  • how to drive people crazy with syslog
  • install powerpill( a pacman wrapper) on Arch Linux
  • Best Google Reader Replacements for Android and Linux
  • python bytecode: single scope
  • macchanger: Ready for the masquerade
  • Clasen: Guadac GTK+ meeting notes
  • Mobile Vim Cheat Sheet
  • Super Ubie Land To Come To Linux Tuesday The 13th!
  • Ground Overlay Rendering Is Here in Marble
  • New in kdepim 4.12: mboximporter

some leftovers:

Filed under
  • Quiet GNU/Linux Revolution in New Zealand
  • Tor advises users to ditch Windows after anonymity-busting attack
  • SUSECon 2013: FIve Big Questions Need Answers
  • UbuntuKylin steals the show at OCOW Summit
  • Thoughts on Quick2
  • Curry all over the C++11
  • Estranged HL2 Single Player Adventure Mod On It's Way To Linux!
  • Florian is Comparing MSO to LibreOffice – Needs YOUR Input
  • Backup And Restore All Installed Packages To CD/DVD Using APTonCD On Ubuntu/Debian
  • set up a Subversion (SVN) server on CentOS or Fedora
  • Pwn probe runs sneaky new Linux distro
  • How to install Steam client on debian 7 (Wheezy)
  • Unvanquished FPS Looks Stunning and It Gets Better with Every New Version
  • "ROSA Planet" switches to rolling release scheme
  • How to become a graphic designer
  • Getting lyrics in Sonata under Ubuntu
  • Best articles to study cat command in Linux
  • AudioCd. Week 7.
  • Destination in sight for Flight Centre's Drupal journey
  • Giada – Audio tool for DJs, live performers and electronic musicians
  • $5 8 GB SD card with NOOBS for Raspberry Pi now available

some odds & ends:

Filed under
  • OS X apps run on Linux with Wine-like emulator for Mac software
  • Open Source Code At Heart of Wall Street Programmer’s Bust
  • Building the open source laptop: fantasy to reality
  • using
  • MEGABYTE PUNCH is now available on PC Mac and Linux
  • Hacktivist Richard Stallman takes on proprietary software, SaaS and open source
  • Qt5 on openSUSE (including experimental KF5 packages)
  • SECRETS OF RÆTIKON to launch on PC, Mac and Linux
  • Firefox 23 Adds Features, Security to Open-Source Browser
Syndicate content

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30