Language Selection

English French German Italian Portuguese Spanish

News feeds blocks

Slashdot
42% (44 votes)
FreshMeat
6% (6 votes)
Linux Games
5% (5 votes)
LWN
2% (2 votes)
lxer.com
7% (7 votes)
NewsForge/Linux.com
1% (1 vote)
Linux Today
9% (10 votes)
Digg Linux/Unix
11% (12 votes)
Other (please comment)
18% (19 votes)
Total votes: 106

Other (Please Comment)

TUXMACHINES \o/

well, i'm subscribed to all of the above, but tuxmachines' feed is the only one i actually read, probably because srlinuxx posts top stories from all of the previouse sites Smile

RSS reader

I subscribed a lot: Distrowatch, tuxmachines, Desktoplinux, Mozilla Links-
I subscribed italian blog too: PuntoInformatico, TuxFeed, IlDisinformatico, pollycoke

------------------------------------------------
I'm looking for SimpliX!
Meet me on http://simplix.wordpress.com (italian)

Why FSDaily of course!

The digg-style site for free software news. You decide what's important, you submit it, you vote for it, you comment on it. Free software news for the free software community by the free software community.

Soon all of the formulas for promotion and burying will be open too so the community can help to find the least biased way to choose the news.

re: FSDaily

I'm actually just trying to see what folks might prefer to see on my side block over there. I gave up on OSNews cuz their rss feed sometimes doesn't update for hours. I like slashdot cuz it covers all sorts of subjects and I click on their headlines quite often. I'm not sure I like Digg, but if a lot of others do...

The trouble with FSDaily is that many times by the time stories end up on there, I've already found them and posted them to my site. I pull it in for myself, but I rarely see anything new there.

So, early results look like folks like Slashdot and Digg.

Give us a chance...

We don't have dedicated people going through news feeds finding news and deciding what to submit. It's a community driven site. The news is slow hitting our homepage at the moment only because we don't have enough active users yet.

However, we have gained over 1000 users in 3 months. Once there are more (active) users. People will (hopefully) be clawing to submit their free-software-related news to our site. Once that happens the news and articles which are important to the community will be there in abundance.

Then it will be the perfect feed for a side block on a free software related site.

I do understand your (and your audience's) leaning toward slashdot or digg though. They expand on the news you publish rather than potentially replicating it.

I, myself, can no longer stand digg. The MS fanboys just make it intolerable. As a foss advocate I find it really hard to see so many mis-informed opinions flying around.

*Edit: and I have noticed that of all the foss related news hubs you are the fastest at picking up the news. Lxer, LWN, digg, fossnews, osnews, etc., seem to be days behind most of the time. From my investigations it seems to be Tuxmachines followed by fsdaily for promptness. This is because: 1) we need more participation, 2) our news stays in the upcoming queue for a while before it hits the home page, 3) possibly because you get up earlier in the morning than some of our contributors, Smile and/or 4)...you never sleep ;P

The ultimate linux news feed

http://www.linuxinsight.com/aggregator aggregates practically all of the above and few more (17 linux news feeds in total).

You can also read 'em in your favorite RSS reader using this RSS feed address: http://feeds.linuxinsight.com/linuxportalnews

I hope you find it useful (all sites are carefully handpicked).

News feeds blocks

Other than tuxmachines, I subscribe to Desktop Linux and Distrowatch feeds.

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