All Jupiter Broadcasting Shows

Jupiter Broadcasting
undefined
Jun 30, 2019 • 0sec

Linux Action News 112

We've got the new Raspberry Pi 4 and share our thoughts, why Microsoft applied to join the linux-distros mailing list, and Ubuntu's 32-bit future is clarified. Plus Mozilla's big plans Firefox on Android, and the future of Steam on Linux.Links:Raspberry Pi 4 Released — Raspberry Pi 4 is now on sale, starting at $35. This is a comprehensive upgrade, touching almost every element of the platform. For the first time we provide a PC-like level of performance for most users, while retaining the interfacing capabilities and hackability of the classic Raspberry Pi line.New version of Raspbian — We are actually releasing it slightly in advance of the official Debian release date. The reason for this is that one of the important new features of Raspberry Pi 4 Slightly faster than Stretch versionNo USB boot yetReinventing Firefox for Android — Today we’re very happy to announce a pilot of our new browser for Android devices that is available to early adopters for testing as of now. Firefox to get a random password generatorMicrosoft applies to join linux-distros mailing list — Windows giant cheered on by Linux Foundation as it seeks membership of private security-focused message board.Register's CoverageIntroducing people.kernel.org — Ever since the demise of Google+, many developers have expressed a desire to have a service that would provide a way to create and manage content in a format that would be more rich and easier to access than email messages sent to LKML. Statement on 32-bit i386 packages for Ubuntu 19.10 and 20.04 LTS — We will put in place a community process to determine which 32-bit packages are needed to support legacy software, and can add to that list post-release if we miss something that is needed.
undefined
Jun 26, 2019 • 0sec

Prospering with Vulkan | BSD Now 304

DragonflyBSD 5.6 is out, OpenBSD Vulkan Support, bad utmp implementations in glibc and FreeBSD, OpenSSH protects itself against Side Channel attacks, ZFS vs OpenZFS, and more. Headlines DragonflyBSD 5.6 is out Version 5.6.0 released 17 June 2019 Version 5.6.1 released 19 June 2019 Big-ticket items Improved VM Informal test results showing the changes from 5.4 to 5.6 are available. Reduce stalls in the kernel vm_page_alloc() code (vm_page_list_find()). Improve page allocation algorithm to avoid re-iterating the same queues as the search is widened. Add a vm_page_hash*() API that allows the kernel to do heuristical lockless lookups of VM pages. Change vm_hold() and vm_unhold() semantics to not require any spin-locks. Change vm_page_wakeup() to not require any spin-locks. Change wiring vm_page's no longer manipulates the queue the page is on, saving a lot of overhead. Instead, the page will be removed from its queue only if the pageout demon encounters it. This allows pages to enter and leave the buffer cache quickly. Refactor the handling of fictitious pages. Remove m->md.pv_list entirely. VM pages in mappings no longer allocate pv_entry's, saving an enormous amount of memory when multiple processes utilize large shared memory maps (e.g. postgres database cache). Refactor vm_object shadowing, disconnecting the backing linkages from the vm_object itself and instead organizing the linkages in a new structure called vm_map_backing which hangs off the vm_map_entry. pmap operations now iterate vm_map_backing structures (rather than spin-locked page lists based on the vm_page and pv_entry's), and will test/match operations against the PTE found in the pmap at the requisite location. This doubles VM fault performance on shared pages and reduces the locking overhead for fault and pmap operations. Simplify the collapse code, removing most of the original code and replacing it with simpler per-vm_map_entry optimizations to limit the shadow depth. DRM Major updates to the radeon and ttm (amd support code) drivers. We have not quite gotten the AMD support up to the more modern cards or Ryzen APUs yet, however. Improve UEFI framebuffer support. A major deadlock has been fixed in the radeon/ttm code. Refactor the startup delay designed to avoid conflicts between the i915 driver initialization and X startup. Add DRM_IOCTL_GET_PCIINFO to improve mesa/libdrm support. Fix excessive wired memory build-ups. Fix Linux/DragonFly PAGE_MASK confusion in the DRM code. Fix idr_*() API bugs. HAMMER2 The filesystem sync code has been rewritten to significantly improve performance. Sequential write performance also improved. Add simple dependency tracking to prevent directory/file splits during create/rename/remove operations, for better consistency after a crash. Refactor the snapshot code to reduce flush latency and to ensure a consistent snapshot. Attempt to pipeline the flush code against the frontend, improving flush vs frontend write concurrency. Improve umount operation. Fix an allocator race that could lead to corruption. Numerous other bugs fixed. Improve verbosity of CHECK (CRC error) console messages. OpenBSD Vulkan Support Somewhat surprisingly, OpenBSD has added the Vulkan library and ICD loader support as their newest port. This new graphics/vulkan-loader port provides the generic Vulkan library and ICD support that is the common code for Vulkan implementations on the system. This doesn't enable any Vulkan hardware drivers or provide something new not available elsewhere, but is rare seeing Vulkan work among the BSDs. There is also in ports the related components like the SPIR-V headers and tools, glsllang, and the Vulkan tools and validation layers. This is of limited usefulness, at least for the time being considering OpenBSD like the other BSDs lag behind in their DRM kernel driver support that is ported over from the mainline Linux kernel tree but generally years behind the kernel upstream. Particularly with Vulkan, newer kernel releases are needed for some Vulkan features as well as achieving decent performance. The Vulkan drivers of relevance are the open-source Intel ANV Vulkan driver and Radeon RADV drivers, both of which are in Mesa though we haven't seen any testing results to know how well they would work if at all currently on OpenBSD, but they're at least in Mesa and obviously open-source. A note: The BSDs are no longer that far behind. FreeBSD 12.0 uses DRM from Linux 4.16 (April 2018), and the drm-devel port is based on Linux 5.0 (March 2019) OpenBSD -current as of April 2019 uses DRM from Linux 4.19.34 *** News Roundup Bad utmp implementations in glibc and freebsd I recently released another version – 0.5.0 – of Dinit, the service manager / init system. There were a number of minor improvements, including to the build system (just running “make” or “gmake” should be enough on any of the systems which have a pre-defined configuration, no need to edit mconfig by hand), but the main features of the release were S6-compatible readiness notification, and support for updating the utmp database. In other words, utmp is a record of who is currently logged in to the system (another file, “wtmp”, records all logins and logouts, as well as, potentially, certain system events such as reboots and time updates). This is a hint at the main motivation for having utmp support in Dinit – I wanted the “who” command to correctly report current logins (and I wanted boot time to be correctly recorded in the wtmp file). I wondered: If the files consist of fixed-sized records, and are readable by regular users, how is consistency maintained? That is – how can a process ensure that, when it updates the database, it doesn’t conflict with another process also attempting to update the database at the same time? Similarly, how can a process reading an entry from the database be sure that it receives a consistent, full record and not a record which has been partially updated? (after all, POSIX allows that a write(2) call can return without having written all the requested bytes, and I’m not aware of Linux or any of the *BSDs documenting that this cannot happen for regular files). Clearly, some kind of locking is needed; a process that wants to write to or read from the database locks it first, performs its operation, and then unlocks the database. Once again, this happens under the hood, in the implementation of the getutent/pututline functions or their equivalents. Then I wondered: if a user process is able to lock the utmp file, and this prevents updates, what’s to stop a user process from manually acquiring and then holding such a lock for a long – even practically infinite – duration? This would prevent the database from being updated, and would perhaps even prevent logins/logouts from completing. Unfortunately, the answer is – nothing; and yes, it is possible on different systems to prevent the database from being correctly updated or even to prevent all other users – including root – from logging in to the system. A good find On FreeBSD, even though write(2) can be asynchronous, once the write syscall returns, the data is in the buffer cache (or ARC), and any future read(2) will see that new data even if it has not yet been written to disk. *** OpenSSH gets an update to protect against Side Channel attacks Last week, Damien Miller, a Google security researcher, and one of the popular OpenSSH and OpenBSD developers announced an update to the existing OpenSSH code that can help protect against the side-channel attacks that leak sensitive data from computer’s memory. This protection, Miller says, will protect the private keys residing in the RAM against Spectre, Meltdown, Rowhammer, and the latest RAMBleed attack. SSH private keys can be used by malicious threat actors to connect to remote servers without the need of a password. According to CSO, “The approach used by OpenSSH could be copied by other software projects to protect their own keys and secrets in memory”. However, if the attacker is successful in extracting the data from a computer or server’s RAM, they will only obtain an encrypted version of an SSH private key, rather than the cleartext version. In an email to OpenBSD, Miller writes, “this change encrypts private keys when they are not in use with a symmetric key that is derived from a relatively large ‘prekey’ consisting of random data (currently 16KB).” ZFS vs OpenZFS You’ve probably heard us say a mix of “ZFS” and “OpenZFS” and an explanation is long-overdue. From its inception, “ZFS” has referred to the “Zettabyte File System” developed at Sun Microsystems and published under the CDDL Open Source license in 2005 as part of the OpenSolaris operating system. ZFS was revolutionary for completely decoupling the file system from specialized storage hardware and even a specific computer platform. The portable nature and advanced features of ZFS led FreeBSD, Linux, and even Apple developers to start porting ZFS to their operating systems and by 2008, FreeBSD shipped with ZFS in the 7.0 release. For the first time, ZFS empowered users of any budget with enterprise-class scalability and data integrity and management features like checksumming, compression and snapshotting, and those features remain unrivaled at any price to this day. On any ZFS platform, administrators use the zpool and zfs utilities to configure and manage their storage devices and file systems respectively. Both commands employ a user-friendly syntax such as‘zfs create mypool/mydataset’ and I welcome you to watch the appropriately-titled webinar “Why we love ZFS & you should too” or try a completely-graphical ZFS experience with FreeNAS. Oracle has steadily continued to develop its own proprietary branch of ZFS and Matt Ahrens points out that over 50% of the original OpenSolaris ZFS code has been replaced in OpenZFS with community contributions. This means that there are, sadly, two politically and technologically-incompatible branches of “ZFS” but fortunately, OpenZFS is orders of magnitude more popular thanks to its open nature. The two projects should be referred to as “Oracle ZFS” and “OpenZFS” to distinguish them as development efforts, but the user still types the ‘zfs’ command, which on FreeBSD relies on the ‘zfs.ko’ kernel module. My impression is that the terms of the CDDL license under which the OpenZFS branch of ZFS is published protects its users from any patent and trademark risks. Hopefully, this all helps you distinguish the OpenZFS project from the ZFS technology. There was further discussion of how the ZFSOnLinux repo will become the OpenZFS repo in the future once it also contains the bits to build on FreeBSD as well during the June 25th ZFS Leadership Meeting. The videos for all of the meetings are available here *** Beastie Bits How to safely and portably close a file descriptor in a multithreaded process without running into problems with EINTR KnoxBug Meetup June 27th at 6pm BSD Pizza Night, June 27th at 7pm, Flying Pie Pizzeria, 3 Monroe Pkwy, Ste S, Lake Oswego, OR Difference between $x and ${x} Beware of Software Engineering Media Sites How Verizon and a BGP optimizer knocked large parts of the internet offline today DragonflyBSD - MDS mitigation added a while ago Reminder: Register for EuroBSDcon 2019 in Lillehammer, Norway Feedback/Questions Dave - CheriBSD Neb - Hello from Norway Lars - Ansible tutorial? Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv *** Your browser does not support the HTML5 video tag.
undefined
Jun 26, 2019 • 0sec

Regolith, Rosa, and Antsy Alien Attack | Choose Linux 12

Two new hosts join Joe to talk about a nice i3 implementation and an amazing arcade game written in Bash. Plus a new segment called Distrohoppers, and a useful hidden feature of GNOME.Links:Regolith Linux — Regolith Linux is a distro for people that prefer a spartan interface with polished and consistent system management. It brings together a trifecta of Ubuntu’s ubiquity, i3-wm’s efficient and productive interface, and Gnome’s system configuration features.Regolith Linux is the i3 Ubuntu Spin You’ve Been Waiting For — Regolith is two things: it’s an Ubuntu-based Linux distro and it’s an installable desktop session. Both approaches share the same aim: make it (a bit) easier to get started with i3 on Ubuntu.Rosa Linux — ROSA Desktop is a Linux distribution featuring a highly customised KDE desktop and a number of modifications designed to enhance the user-friendliness of the working environment.Antsy Alien Attack! — A game, written in Bash, that is a somewhat retro-a-like shoot 'em up. Hopefully.QJoyPad — A simple Linux/QT program that lets you use your gaming devices where you want them: in your games!Ubuntu Podcast S12E10.5 @ FOSS Talk Live 2019 — Mark, Alan and Martin from Ubuntu Podcast have each been working on a secret coding challenge. All is revealed before a live audience at FOSS Talk Live 2019!How to use Gnome shell’s secret screen recorder — In this article, we will see how to use a Gnome shell’s secret screen recorder.
undefined
Jun 25, 2019 • 0sec

What's your NextCloud? | LINUX Unplugged 307

Go full self-hosted with our team’s tips, and we share our setups from simple to complex. Plus what really happens on a 64-bit Linux box when you run 32-bit software, some very handy picks, our reaction to the new Raspberry Pi 4 and more.Special Guests: Alex Kretzschmar and Brent Gervais.Links:These 5D Glass Discs Store 360 TB Of Data For 13.8 Billion Years — Researchers at the University of Southampton have showcased their new nanostructured glass discs that have the ability to store digital data for billions of years. The university announced that they've managed to build a device that can store huge amounts of data on small glass discs using laser writingThe Raspberry Pi 4 launch site runs on a Pi 4 cluster | Ars Technica — The Raspberry Pi 4 Model B has launched. It's a pretty big upgrade from the Raspberry Pi 3, with the company claiming that the device can provide "desktop performance comparable to entry-level x86 PC systems."Is 4 GB The Limit For The Raspberry Pi 4? | Hackaday — It’s not the lack of an Oxford comma that caught his eye, but the tantalising mention of an 8 GB Raspberry Pi 4. Could we one day see an extra model in the range with twice the memory? It would be nice to think so. Buy a Raspberry Pi 4 Desktop Kit – Raspberry Pi — Full desktop computer kit - just connect to HDMI display(s) Steam is dropping support for Ubuntu, but not Linux entirely | PC Gamer — Last Friday, a developer at Valve announced that Ubuntu Linux 19.10⁠—which is due to come out this October—won't be supported by Steam. Valve is still supporting Linux, just not future versions of the Ubuntu operating system. Pierre-Loup Griffais on Twitter — Ubuntu 19.10 and future releases will not be officially supported by Steam or recommended to our users. We will evaluate ways to minimize breakage for existing users, but will also switch our focus to a different distribution, currently TBD.Statement on 32-bit i386 packages for Ubuntu 19.10 and 20.04 LTS | Ubuntu — Thanks to the huge amount of feedback this weekend from gamers, Ubuntu Studio, and the WINE community, we will change our plan and build selected 32-bit i386 packages for Ubuntu 19.10 and 20.04 LTS. What it takes to run a 32-bit x86 program on a 64-bit x86 Linux system — Suppose that you have a modern 64-bit x86 Linux system (often called an x86_64 environment) and that you want to run an old 32-bit x86 program on it (a plain x86 program). What does this require from the overall system, both the kernel and the rest of the environment?Nextcloud — The self-hosted productivity platform that keeps you in control NextCloud Phone SyncNextCloud workflow scriptsNextcloud Registration PluginNextCloud Keep or SweepNextcloud NewsNextcloud file-drop — Convenient and secure file exchange for enterprises.Install Nextcloud for Linux using the Snap StoreNextCloud docker-compose examplesLinuxServer.io NextCloud docker imageCSRF Check Failed · Issue #768 · nextcloud/ioslexicon — Manipulate DNS records on various DNS providers in a standardized way. ARandR: Another XRandR GUI — ARandR is designed to provide a simple visual front end for XRandR. Relative monitor positions are shown graphically and can be changed in a drag-and-drop way.
undefined
Jun 24, 2019 • 0sec

Find Your Off-Ramp | Coder Radio 363

We take on the issues of burnout, work communication culture, and keeping everything in balance. Plus Wes asks 'Why Not Kotlin' and breaks down where it fits in his toolbox.Links:Kotlin overview — Kotlin is an open-source, statically-typed programming language that supports both object-oriented and functional programming. Kotlin provides similar syntax and concepts from other languages, including C#, Java, and Scala, among many others. Kotlin does not aim to be unique—instead, it draws inspiration from decades of language development. It exists in variants that target the JVM (Kotlin/JVM), JavaScript (Kotlin/JS), and native code (Kotlin/Native).Kotlin/Native — Kotlin/Native is a technology for compiling Kotlin code to native binaries, which can run without a virtual machine. It is an LLVM based backend for the Kotlin compiler and native implementation of the Kotlin standard library. Kotlin for JavaScript — Kotlin provides the ability to target JavaScript. It does so by transpiling Kotlin to JavaScript. The current implementation targets ECMAScript 5.1 but there are plans to eventually target ECMAScript 2015 as well. My favorite examples of functional programming in Kotlin — One of the great things about Kotlin is that it supports functional programming. Let’s see and discuss some simple but expressive functions written in Kotlin. Arrow: Functional companion to Kotlin's Standard Library — Arrow aims to provide a lingua franca of interfaces and abstractions across Kotlin libraries. For this, it includes the most popular data types, type classes and abstractions such as Option, Try, Either, IO, Functor, Applicative, Monad to empower users to write pure FP apps and libraries built atop higher order abstractions. Awesome Kotlin Resources — The ultimate resource list for your most loved coding language. awesome-kotlin — A curated list of awesome Kotlin frameworks, libraries, documents and other resourcesReddit Co-Founder Alexis Ohanian Warns Always-On Work Culture Creating ‘Broken’ People - WSJ — “I’ve spoken out quite a bit about things like ‘hustle porn,’ and this ceremony of showing off on social [media] about how hard you’re working,” said Mr. Ohanian, who previously co-founded online discussion forum Reddit. “Y’all see it on Instagram and you certainly see it in the startup community, and it becomes really toxic.”Thread by @mwseibel — I’ve noticed that many people compete in games they don’t understand because they are modeling the behavior of people around them. Most common is the competition for wealth as a proxy for happiness.Understanding Burnout Meetup — You may not know it yet, but IT is not easy. Breakdowns in people, processes, and technology leads to frustrating times for all of us. As it spirals out of control, we often meet the final boss: burnout. Linux Academy is Hiring!
undefined
Jun 24, 2019 • 0sec

Random Access Memories | The Friday Stream 8

We share the stories of our very first computers, and reminisce about the bad old days of the PC. Plus we solve another world problem, explain Amazon Flex, and our cheap home studio build.Links:Music - NewRetroWaveHorse Blood - NewRetroWaveEnd of The Night - NewRetroWaveAngela Fisher on Instagram — Here we are! Last day of school!!!What It's Like To Be An Amazon Flex Delivery Driver — Amazon has offered free two-day shipping for Prime members since 2005. As Amazon rolls out a one-day shipping guarantee for its 100 million Prime members, Amazon Flex drivers help solve the company's last mile problem. CNBC spoke to these on-demand contract workers all over the country to find out what it's really like to deliver for Amazon.The Computer Chronicles - Pentium PCs (1993)V.92 - Wikipedia — V.92 is an ITU-T recommendation, titled Enhancements to Recommendation V.90, that establishes a modem standard allowing near 56 kb/s download and 48 kb/s upload rates. With V.92 PCM is used for both the upstream and downstream connections; previously 56K modems only used PCM for downstream data.Paratrooper DOS Game — Paratrooper is a 1982 computer game, written by Greg Kuperberg and published by Orion Software. Paratrooper is one of the three games written by Greg Kuperberg when the IBM-PC was still very new.Floppy disk - Wikipedia — A floppy disk, also known as a floppy, diskette, or simply disk, is a type of disk storage composed of a disk of thin and flexible magnetic storage medium, sealed in a rectangular plastic enclosure lined with fabric that removes dust particles. Macintosh SE/30, start and format a floppy disk - Sounds Of Changes — The Macintosh SE/30 is a personal computer that was designed, manufactured and sold by Apple Computer, Inc. from 1989 until 1991.No, Your Kid Isn't Growing Horns Because Of Cellphone Use | Techdirt — This week, the Washington Post grabbed plenty of attention for a story that claimed that kids are actually growing "horns" because of cell phone use. The story, which leans on 2016 and 2018 research out of Australia, was cribbing off of this more nuanced piece by the BBC on how skeletal adaptation to modern living changes are kind of a thing.Australian researchers find 'horns' growing on young people's skulls from phone overuse - The Washington PostYes Kids are Growing Horns - But the Solution is Simple - YouTube — Recently this has become big news with many media outlets reporting on it. It may sound sensationalist, but it really isn't. This is a serious symptom of the augmented lifestyle young people are living involving their phones and media devices.
undefined
Jun 23, 2019 • 0sec

Linux Action News 111

Ubuntu sets the Internet on fire, new Linux and FreeBSD vulnerabilities raise concern, while Mattermost raises $50M to compete with Slack. Plus we react to Facebook's Libra confirmation and the end of Google tablets.Links:Ubuntu to drop i386 architecture — he Ubuntu engineering team has reviewed the facts before us and concluded that we should not continue to carry i386 forward as an architecture. Consequently, i386 will not be included as an architecture for the 19.10 release, and we will shortly begin the process of disabling it for the eoan series across Ubuntu infrastructure.Proposal: Let's drop i386 May 9th 2018Proposal: Let's drop i386 May 14th 2018Wine devs worried — "I think not building packages for Ubuntu 19.10 would be the only practical option. It would probably be good to have a small explanation on the download page though. As I understand it, it would still be possible to run 32-bit executables on the Ubuntu 19.10 kernel, but we'd have to build and ship all our dependencies ourselves. I don't think we want to go there just yet." At least some games not working without 32-bit — Further to the recent announcement and subsequent discussion, I did a little testing over lunch on eoan 19.10 with all i386 packages removed and the i386 part of the repo disabled.Ubuntu NOT “dropping support for i386 applications” — What we are dropping is updates to the i386 libraries, which will be frozen at the 18.04 LTS versions. But there is every intention to ensure that there is a clear story for how i386 applications (including games) can be run on versions of Ubuntu later than 19.10.Petition · Dont remove 32 bit support in the next version of UbuntuTest and run multiple instances of snapsOpenMandriva also dropping 32-bitNew vulnerabilities may let hackers remotely SACK Linux and FreeBSD systems — Netflix researchers discovered 4 flaws that could wreak havoc in data centers.Linux devices vulnerable to ping of death attackRed Hat's take on TCP SACK PANICMattermost raises $50M — The capital infusion follows a $20 million series A in February and a $3.5 million seed round in February 2017 and brings the Palo Alto, California-based company’s total raised to roughly $70 million.Google says it’s done making tablets — The Pixel Slate won’t get a sequel, but the Pixelbook willFacebook's Libra confirmed — Facebook is planning to launch a cryptocurrency it hopes will “transform the global economy.”
undefined
Jun 23, 2019 • 0sec

SACK Attack | TechSNAP 406

A new vulnerability may be the next 'Ping of Death'; we explore the details of SACK Panic and break down what you need to know. Plus Firefox zero days targeting Coinbase, the latest update on Rowhammer, and a few more reasons it's a great time to be a ZFS user.Links:SACK Panic Security Bulletin — Netflix has identified several TCP networking vulnerabilities in FreeBSD and Linux kernels. The vulnerabilities specifically relate to the Maximum Segment Size (MSS) and TCP Selective Acknowledgement (SACK) capabilities. The most serious, dubbed “SACK Panic,” allows a remotely-triggered kernel panic on recent Linux kernels.Ubuntu SACK Panic Guidance — You should update your kernel to the versions specified below in the Updates section and reboot. Alternatively, Canonical Livepatch updates will be available to mitigate these two issues without the need to reboot. Red Hat SACK Panic Advisory — Red Hat customers running affected versions of these Red Hat products are strongly recommended to update them as soon as errata are available. Customers are urged to apply the available updates immediately and enable the mitigations as they feel appropriate.    RFC 2018 - TCP Selective Acknowledgment Options — TCP may experience poor performance when multiple packets are lost from one window of data. With the limited information available from cumulative acknowledgments, a TCP sender can only learn about a single lost packet per round trip time. An aggressive sender could choose to retransmit packets early, but such retransmitted segments may have already been successfully received. A Selective Acknowledgment (SACK) mechanism, combined with a selective repeat retransmission policy, can help to overcome these limitations.Ping of Death — In a nutshell, it is possible to crash, reboot or otherwise kill a large number of systems by sending a ping of a certain size from a remote machine.Firefox zero-day was used in attack against Coinbase employees, not its users | ZDNet — A recent Firefox zero-day that has made headlines across the tech news world this week was actually used in attacks against Coinbase employees, and not the company's users.Mozilla fixes second Firefox zero-day exploited in the wild | ZDNet — Mozilla has released a second security update this week to patch a second zero-day that was being exploited in the wild to attack Coinbase employees and other cryptocurrency organizations. RAMBleed — RAMBleed is a side-channel attack that enables an attacker to read out physical memory belonging to other processes. The implications of violating arbitrary privilege boundaries are numerous, and vary in severity based on the other software running on the target machine. As an example, in our paper we demonstrate an attack against OpenSSH in which we use RAMBleed to leak a 2048 bit RSA key. Digging into the new features in OpenZFS post-Linux migration | Ars Technica — One of the most important new features in 0.8 is Native ZFS Encryption. Until now, ZFS users have relied on OS-provided encrypted filesystem layers either above or below ZFS. While this approach does work, it presented difficulties.Allan Jude on Twitter — Once the FreeBSDs are upstreamed, everything is changing to 'OpenZFS', including the github organization currently know as 'zfsonlinux'.ZFS on Linux ReleasesLinux Academy is hiring!
undefined
Jun 20, 2019 • 0sec

Delete Your Community | User Error 68

Two #AskError specials in a row! Advice for our younger selves, leaving communities, our listening habits, and hoarding. Plus the most serious question that’s ever been asked on the show, and more. 00:00:42 What's the one bit of Linux advice you'd give yourself if you could go back to the start of your journey? 00:04:17 What would make you delete your Twitter account? 00:11:29 When do you think you’ll buy your first electric car? 00:19:06 Have you ever been banned from a community? 00:25:39 What kind of printer cartridges do you buy? 00:30:27 How many podcasts do you listen to? 00:33:42 What do you hoard, but probably shouldn't?
undefined
Jun 19, 2019 • 0sec

OpenZFS in Ports | BSD Now 303

Headlines ZFSonFreeBSD ports renamed OpenZFS The ZFS on FreeBSD project has renamed the userland and kernel ports from zol and zol-kmod to openzfs and openzfs-kmod The new versions from this week are IOCTL compatible with the command line tools in FreeBSD 12.0, so you can use the old userland with the new kernel module (although obviously not the new features) With the renaming it is easier to specify which kernel module you want to load in /boot/loader.conf: > zfs_load=”YES” or > openzfs_load=”YES” To load traditional or the newer version of ZFS The kmod still requires FreeBSD 12-stable or 13-current because it depends on the newer crypto support in the kernel for the ZFS native encryption feature. Allan is looking at ways to work around this, but it may not be practical. We would like to do an unofficial poll on how people would the userland to co-exist. Add a suffix to the new commands in /usr/local (zfs.new zpool.new or whatever). One idea i’ve had is to move the zfs and zpool commands to /libexec and make /sbin/zfs and /sbin/zpool a switcher script, that will call the base or ports version based on a config file (or just based on if the port is installed) For testing purposes, generally you should be fine as long as you don’t run ‘zpool upgrade’, which will make your pool only importable using the newer ZFS. For extra safety, you can create a ‘zpool checkpoint’, which will allow you to undo any changes that are made to the pool during your testing with the new openzfs tools. Note: the checkpoint will undo EVERYTHING. So don’t save new data you want to keep. Note: Checkpoints disable all freeing operations, to prevent any data from being overwritten so that you can re-import at the checkpoint and undo any operation (including zfs destroy-ing a dataset), so also be careful you don’t run out of space during testing. Please test and provide feedback. How to use blacklistd(8) with NPF as a fail2ban replacement About blacklistd(8) blacklistd(8) provides an API that can be used by network daemons to communicate with a packet filter via a daemon to enforce opening and closing ports dynamically based on policy. The interface to the packet filter is in /libexec/blacklistd-helper (this is currently designed for npf) and the configuration file (inspired from inetd.conf) is in etc/blacklistd.conf Now, blacklistd(8) will require bpfjit(4) (Just-In-Time compiler for Berkeley Packet Filter) in order to properly work, in addition to, naturally, npf(7) as frontend and syslogd(8), as a backend to print diagnostic messages. Also remember npf shall rely on the npflog* virtual network interface to provide logging for tcpdump() to use. Unfortunately (dont' ask me why :P) in 8.1 all the required kernel components are still not compiled by default in the GENERIC kernel (though they are in HEAD), and are rather provided as modules. Enabling NPF and blacklistd services would normally result in them being automatically loaded as root, but predictably on securelevel=1 this is not going to happen News Roundup [WIP] raidz expansion, alpha preview 1 Motivation and Context > This is a alpha-quality preview of RAID-Z expansion. This feature allows disks to be added one at a time to a RAID-Z group, expanding its capacity incrementally. This feature is especially useful for small pools (typically with only one RAID-Z group), where there isn't sufficient hardware to add capacity by adding a whole new RAID-Z group (typically doubling the number of disks). > For additional context as well as a design overview, see my short talk from the 2017 OpenZFS Developer Summit: slides video Rant: running audio VU-meter increases my CO2 footprint A couple months ago I noticed that the monitor on my workstation never power off anymore. Screensaver would go on, but DPMs (to do the poweroff) never kicked in. I grovels the output of various tools that display DPMS settings, which as usual in Xorg were useless. Everybody said DPMS is on with a timeout. I even wrote my own C program to use every available Xlib API call and even the xscreensaver library calls. (should make it available) No go, everybody says that DPMs is on, enabled and set on a timeout. Didn’t matter whether I let xscreeensaver do the job or just the X11 server. After a while I noticed that DPMS actually worked between starting my X11 server and starting all my clients. I have a minimal .xinitrc and start the actual session from a script, that is how I could notice. If I used a regular desktop login I wouldn’t have noticed. A server state bug was much more likely than a client bug. See the article for the rest... XSAVE and compat32 kernel work for LLDB Upstream describes LLDB as a next generation, high-performance debugger. It is built on top of LLVM/Clang toolchain, and features great integration with it. At the moment, it primarily supports debugging C, C++ and ObjC code, and there is interest in extending it to more languages. In February, I have started working on LLDB, as contracted by the NetBSD Foundation. So far I've been working on reenabling continuous integration, squashing bugs, improving NetBSD core file support and lately extending NetBSD's ptrace interface to cover more register types. You can read more about that in my Apr 2019 report. In May, I was primarily continuing the work on new ptrace interface. Besides that, I've found and fixed a bug in ptrace() compat32 code, pushed LLVM buildbot to ‘green’ status and found some upstream LLVM regressions. More below. Some things about where icons for modern X applications come from If you have a traditional window manager like fvwm, one of the things it can do is iconify X windows so that they turn into icons on the root window (which would often be called the 'desktop'). Even modern desktop environments that don't iconify programs to the root window (or their desktop) may have per-program icons for running programs in their dock or taskbar. If your window manager or desktop environment can do this, you might reasonably wonder where those icons come from by default. Although I don't know how it was done in the early days of X, the modern standard for this is part of the Extended Window Manager Hints. In EWMH, applications give the window manager a number of possible icons, generally in different sizes, as ARGB bitmaps (instead of, say, SVG format). The window manager or desktop environment can then pick whichever icon size it likes best, taking into account things like the display resolution and so on, and display it however it wants to (in its original size or scaled up or down). How this is communicated in specific is through the only good interprocess communication method that X supplies, namely X properties. In the specific case of icons, the _NET_WM_ICON property is what is used, and xprop can display the size information and an ASCII art summary of what each icon looks like. It's also possible to use some additional magic to read out the raw data from _NET_WM_ICON in a useful format; see, for example, this Stackoverflow question and its answers. Beastie Bits Recent Security Innovations Old Unix books + Solaris Pro-Desktop - A Tiling Desktop Environment The Tar Pipe At least one vim trick you might not know Feedback/Questions Johnny - listener feedback Brian - Questions Mark - ZFS Question Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Your browser does not support the HTML5 video tag.

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
Get the app