|
|
Subscribe / Log in / New account

Brief items

Security

Sandboxing in Linux with zero lines of code (Cloudflare blog)

The Cloudflare blog is running an overview of sandboxing with seccomp(), culminating in a tool written there to sandbox any existing program. "We really liked the 'zero code seccomp' approach with systemd SystemCallFilter= directive, but were not satisfied with its limitations. We decided to take it one step further and make it possible to prohibit any system call in any process externally without touching its source code, so came up with the Cloudflare sandbox. It’s a simple standalone toolkit consisting of a shared library and an executable. The shared library is supposed to be used with dynamically linked applications and the executable is for statically linked applications."

Comments (9 posted)

Security quotes of the week

So it seems incredibly likely that any effort to bar TikTok would raise a whole bunch of legal concerns -- starting with a basic 1st Amendment concern. The US government can't just say "you can't use that social media app." That may be how things work in China or India, but not in the US. And, of course, it would likely set off a chain reaction elsewhere as well. China already bans most major US apps and services, but we're still dealing with a pointless trade war that would only be exacerbated by such a move.

There are plenty of reasons to be concerned about TikTok, it's connections to China, and the security of the app. But none of that means that the US government has the right to just ban it. While Trump may want to pretend he's a dictator, and Pompeo may want to pretend he works for a dictator, that's not how any of this works.

Mike Masnick

The list, which was published on a popular hacking forum, includes each device's IP address, along with a username and password for the Telnet service, a remote access protocol that can be used to control devices over the internet.

According to experts to who ZDNet spoke this week, and a statement from the leaker himself, the list was compiled by scanning the entire internet for devices that were exposing their Telnet port. The hacker then tried using (1) factory-set default usernames and passwords, or (2) custom, but easy-to-guess password combinations.

Catalin Cimpanu on ZDNet

As with pretty much everything else, you can assume that if an industry lobbying group is in favor of it, then it doesn't go far enough.

And if you need more security and privacy principles for the IoT, here's a list of over twenty.

Bruce Schneier comments on the Business Software Alliance IoT security principles [PDF]

Comments (none posted)

Kernel development

Kernel release status

The current development kernel is 5.8-rc4, released on July 5. Linus said: "The end result is that it's been fairly calm, and there's certainly been discussion of upcoming fixes, but I still have the feeling that 5.8 is looking fairly normal and things are developing smoothly despite the size of this release."

It's worth noting that the 5.8-rc5 release will raise the minimum GCC requirement to version 4.9.

Stable updates: none have been released in the last week. The relatively small 5.7.8, 5.4.51, 4.19.132, 4.14.188, 4.9.230, and 4.4.230 updates are all in the review process; they are due on July 9.

Comments (none posted)

Quote of the week

Because we are relying on things that are not guaranteed by the C memory model, we need to pay attention to the implementations. As I have said elsewhere, the price of control dependencies is eternal vigilance.
Paul McKenney

Comments (none posted)

Distributions

OpenSUSE Leap 15.2 released

The openSUSE Leap 15.2 release is now available; see the announcement for a long list of new features. "In general, software packages in the distribution grew by the hundreds. Data fusion, Machine Learning and AI aren't all that is new in openSUSE Leap 15.2; a Real-Time Kernel for managing the timing of microprocessors to ensure time-critical events are processed as efficiently as possible is available in this release."

Comments (7 posted)

Distribution quote of the week

That said, I am not against sd-boot, btrfs, nano or a bunch of other changes which seem to have gotten every 'stop the change' advocate out there. I understand a little of where they are coming from... fixing things are hard enough at times. I also understand what it is like to be overloaded with everything going on these days and just want things to stop for a bit. The problem is that doesn't happen, and it definitely doesn't happen in Fedora. If people need a slower or stopped OS, there is CentOS or Debian Stable. Fedora isn't as bleeding edge as other Linux distributions... but it is constantly moving and it is always going to be a bumpy road.
Stephen J Smoogen

Comments (none posted)

Development

Book: Perl 7: A Risk-Benefit Analysis

Dan Book has done a detailed analysis of the Perl 7 transition. "Large amount of CPAN modules will not work in Perl 7; plans for working around this would either involve every affected CPAN author, which is a virtual impossibility for the stated 1 year time frame; or the toolchain group, a loose group of people who each maintain various modules and systems that are necessary for CPAN to function, who either have not been consulted as of yet or have not revealed their plans related to the tools they maintain. Going into this potential problem sufficiently would be longer than this blog post, but suffice to say that a Perl where highly used CPAN modules don't seamlessly work is not Perl."

Comments (23 posted)

Development quote of the week

Now, why should we care about an old bridge? It's because there's a universal truth about software development that software engineers don't like to talk about too much.

We're really bad at writing software.

[...] But the people who design and build bridges, they're great at it. Bridges get built on time, on budget, and last for dozens, hundreds, even thousands of years. Bridge building is, if you think about it, kind of awesome. And bridges are such a common occurrence that they’re also incredibly boring. No one is amazed when a bridge works correctly, and everyone is kind of amazed when software does.

Unfortunately, the world is very dependent on software. It might even depend more on software than it does on bridges. So we have to get better at writing software far faster than we got good at building bridges.

Jon Bodner

Comments (10 posted)

Miscellaneous

LPC town hall #2: the kernel report

The Linux Plumbers Conference has announced the second in a brief series of "town hall" events leading up to the full (virtual) conference starting August 24. This one features LWN editor Jonathan Corbet presenting a version of his "Kernel Report" talk covering the current and future state of the kernel-development community. This talk is scheduled for July 16 at 9:00AM US/Mountain time (8:00AM US/Pacific, 3:00PM UTC). Mark your calendars.

Comments (3 posted)

The "Open Usage Commons" launches

Google has announced the creation of the Open Usage Commons, which is intended to help open-source projects manage their trademarks. From the organization's own announcement: "We created the Open Usage Commons because free and fair open source trademark use is critical to the long-term sustainability of open source. However, understanding and managing trademarks takes more legal know-how than most project maintainers can do themselves. The Open Usage Commons is therefore dedicated to creating a model where everyone in the open source chain – from project maintainers to downstream users to ecosystem companies – has peace of mind around trademark usage and management. The projects in the Open Usage Commons will receive support specific to trademark protection and management, usage guidelines, and conformance testing." Initial members include the Angular, Gerrit, and Istio projects.

Comments (6 posted)

Page editor: Jake Edge
Next page: Announcements>>


Copyright © 2020, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds