Podcast appearances and mentions of Brian Behlendorf

Back again by popular demand, here are more tales from Burning Man's oral history project, an ambitious endeavor to track down and talk with people who helped shape the culture as we now know it.Stuart and Andie share stories of early technology on the playa, and on the internet.Andie Grace aka Actiongrl interviews from the vantage of having co-created Burning Man's world of communications, from Media Mecca to this very podcast.Brian Behlendorf - technologist and open-source software pioneer. He developed Burning Man's online presence and connected people through the venn diagram of luminaries from SF Raves, to Wired Magazine to the Apache Software Foundation.David Beach - designer, creative director, and instigator of the impossible with early dynamic content on the web. He helped create Burning Man's first live streaming and web presence.Scott Beale - documentarian, founder of Laughing Squid, subculture super-connector of various tentacles of the meta-scene.Stuart Magrum - zinester, cacophonist, billboard liberator, Minister of Propaganda, Director of the Philosophical Center, publisher of the first on-site newspaper of Burning Man (the Black Rock Gazette), and always in the same place at the same time as the characters in these stories of Burning Man's media experiments.Andie GraceBrian BehlendorfDavid BeachScott BealeStuart MangrumLaughing Squid: Burning Man 1996 Netcastdispatch2023.burningman.orgjournal.burningman.org/philosophical-centerburningman.org/programs/philosophical-centerBurning Man Live: A People's History of Burning Man - Volume 2Burning Man Live: A People's History of Burning Man - Volume 1 LIVE.BURNINGMAN.ORG

The early days of the internet were characterized by challenges in finding and disseminating information, which has now shifted to the problem of information overload. Linux Foundations' Brian Behlendorf shares his take on establishing identity and building trust in AI models. This episode is sponsored by Consensus 2024 Now Available for pre-order | Michael Casey's New Book with Frank H. McCourt, their forthcoming book: Our Biggest Fight: Reclaiming Liberty, Humanity, and Dignity in the Digital AgeIn this episode of "Money Reimagined," hosts Michael Casey and Sheila Warren are joined by Brian Behlendorf, Head of AI Strategy at the Linux Foundation and CTO of the Open Wallet Foundation, to discuss the early internet era and its lessons. They cover challenges in disseminating information, the shift to centralization, and the importance of trust and decentralization. They also address open-source software, AI model openness, and the future of technology, emphasizing the need for inclusive and trustworthy digital ecosystems.Chapters | 00:00 Introduction and Background03:01 Lessons from the Early Days of the Internet08:10 Rethinking Trust and Decentralization12:36 The Role of Open Source Software22:23 Addressing the Challenges of Technology25:33 Navigating the Flood of Information27:33 Establishing Identity and Trust34:33 The Potential of the Metaverse39:16 Empowering Technology for Inclusive ExperiencesLinks | Linux Foundation Crypto Council for Innovation CoinDesk.com-Consensus is where experts convene to talk about the ideas shaping our digital future. Join developers, investors, founders, brands, policymakers and more in Austin, Texas from May 29-31. The tenth annual Consensus is curated by CoinDesk to feature the industry's most sought-after speakers, unparalleled networking opportunities and unforgettable experiences. Take 15% off registration with the code MRP15. Register now at consensus.coindesk.com-Money Reimagined has been produced and edited by senior producer Michele Musso and our executive producer is Jared Schwartz. Our theme song is “The News Tonight ” by Shimmer. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

The early days of the internet were characterized by challenges in finding and disseminating information, which has now shifted to the problem of information overload. Linux Foundations' Brian Behlendorf shares his take on establishing identity and building trust in AI models. This episode is sponsored by Consensus 2024 Now Available for pre-order | Michael Casey's New Book with Frank H. McCourt, their forthcoming book: Our Biggest Fight: Reclaiming Liberty, Humanity, and Dignity in the Digital AgeIn this episode of "Money Reimagined," hosts Michael Casey and Sheila Warren are joined by Brian Behlendorf, Head of AI Strategy at the Linux Foundation and CTO of the Open Wallet Foundation, to discuss the early internet era and its lessons. They cover challenges in disseminating information, the shift to centralization, and the importance of trust and decentralization. They also address open-source software, AI model openness, and the future of technology, emphasizing the need for inclusive and trustworthy digital ecosystems.Chapters | 00:00 Introduction and Background03:01 Lessons from the Early Days of the Internet08:10 Rethinking Trust and Decentralization12:36 The Role of Open Source Software22:23 Addressing the Challenges of Technology25:33 Navigating the Flood of Information27:33 Establishing Identity and Trust34:33 The Potential of the Metaverse39:16 Empowering Technology for Inclusive ExperiencesLinks | Linux Foundation Crypto Council for Innovation CoinDesk.com-Consensus is where experts convene to talk about the ideas shaping our digital future. Join developers, investors, founders, brands, policymakers and more in Austin, Texas from May 29-31. The tenth annual Consensus is curated by CoinDesk to feature the industry's most sought-after speakers, unparalleled networking opportunities and unforgettable experiences. Take 15% off registration with the code MRP15. Register now at consensus.coindesk.com-Money Reimagined has been produced and edited by senior producer Michele Musso and our executive producer is Jared Schwartz. Our theme song is “The News Tonight ” by Shimmer. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

The Linux Foundation's Open Source Security Foundation (OSSF) is addressing the challenge of timely software component updates to prevent security vulnerabilities like Log4J. In an interview with Alex Williams of The New Stack at the Open Source Summit in Vancouver, Omkhar Arasaratnam, the new general manager of OSSF, and Brian Behlendorf, CTO of OSSF, discuss the importance of making software secure from the start and the need for rapid response when vulnerabilities occur. In this conversation, they highlight the significance of Software Bill of Materials (SBOMs), which provide a complete list of software components and supply chain relationships. SBOMs offer data that can aid decision-making and enable reputation tracking of repositories. The interview also touches on the issues with package managers and the quantification of software vulnerability risks. Overall, the goal is to improve the efficiency and effectiveness of software component updates and leverage data to enhance security in enterprise and production environments.Learn more from The New Stack:Creating a 'Minimum Elements' SBOM Document in 5 MinutesEnhance Your SBOM Success with SLSA

In this episode, we conclude our miniseries dealing with software supply chain security by considering the next five years in the space, what we need, and what we can hope for. Emily Fox, Aeva Black, Brian Behlendorf, Adrian Ludwig, Lena Smart, and of course Guy Podjarny, join Simon by sharing some insights on the areas in most need of attention, and where we can realistically expect to make progress in the near future. Listeners will hear about trust and tooling, downstream complexities, and qualifying security engineers, with the conversation ending on an optimistic note with an eye to the horizon. For most of our panel, the message of consistent attention and security prioritisation within organisations, as well as from governance is paramount to the health of any of these systems. So to hear it all in this final installment of our special, be sure to press play now!

When we stop to think about the software running in our production environments, a large proportion of it is very likely open source. Are there effective mechanisms to truly understand and have visibility into all of these libraries? How do you ensure that these libraries are secure? To answer these questions, we feature input from Guy Podjarny, Lena Smart, Brian Behlendorf, Aeva Black, Emily Fox, Jim Zemlin, David Wheeler and Simon Maple as we dissect some key terms and promising projects in the software supply chain security space. Tuning in, you'll learn what the term SBOM means, why the problem of securing the open-source pipeline is such a complex one, and what organizations like the Open Source Software Foundation (SSF) and Open Source Initiative (OSI) are doing to address it. We also introduce some key players that can provide you with assistance as you work to improve your own open-source security or software supply chain security posture. For all this and more, you won't want to miss part two of The Secure Developer's software supply chain security series! 

This week in the Security News: GetVariable strikes again, attackers could blow up your computer remotely, escaping containers, null-dereferences and faulty evaluations, 31 new CPU vulnerabilities for AMD, a look into Chrome, santa, not-so-secure secure booting, and malware included!   Open source is the bedrock of most of the world's software today, so how to raise the floor on software quality across the industry? First, we need better tools to measure the trustworthiness of code based on objective measures, processes that encourage better security practices by developers, and tools and processes that encourage teamwork and shared responsibility for security. Several efforts are underway in major open source communities to address these issues. At the Open Source Security Foundation (OpenSSF), major companies, open source software maintainers, startup companies and government actors are working together to improve open source software supply chain security. Brian will share his view of this landscape, detail the work being done at the OpenSSF, show where those efforts are already bearing fruit, and demonstrate what you and your organization can (must!) do to participate in these efforts. Segment Resources: https://openssf.org/   Visit https://www.securityweekly.com/psw for all the latest episodes! Visit https://securityweekly.com/acm to sign up for a demo or buy our AI Hunter! Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly   Show Notes: https://securityweekly.com/psw770

Open source is the bedrock of most of the world's software today, so how to raise the floor on software quality across the industry? First, we need better tools to measure the trustworthiness of code based on objective measures, processes that encourage better security practices by developers, and tools and processes that encourage teamwork and shared responsibility for security. Several efforts are underway in major open source communities to address these issues. At the Open Source Security Foundation (OpenSSF), major companies, open source software maintainers, startup companies and government actors are working together to improve open source software supply chain security. Brian will share his view of this landscape, detail the work being done at the OpenSSF, show where those efforts are already bearing fruit, and demonstrate what you and your organization can (must!) do to participate in these efforts. Segment Resources: https://openssf.org/   Visit https://www.securityweekly.com/psw for all the latest episodes! Show Notes: https://securityweekly.com/psw770

This week in the Security News: GetVariable strikes again, attackers could blow up your computer remotely, escaping containers, null-dereferences and faulty evaluations, 31 new CPU vulnerabilities for AMD, a look into Chrome, santa, not-so-secure secure booting, and malware included!   Open source is the bedrock of most of the world's software today, so how to raise the floor on software quality across the industry? First, we need better tools to measure the trustworthiness of code based on objective measures, processes that encourage better security practices by developers, and tools and processes that encourage teamwork and shared responsibility for security. Several efforts are underway in major open source communities to address these issues. At the Open Source Security Foundation (OpenSSF), major companies, open source software maintainers, startup companies and government actors are working together to improve open source software supply chain security. Brian will share his view of this landscape, detail the work being done at the OpenSSF, show where those efforts are already bearing fruit, and demonstrate what you and your organization can (must!) do to participate in these efforts. Segment Resources: https://openssf.org/   Visit https://www.securityweekly.com/psw for all the latest episodes! Visit https://securityweekly.com/acm to sign up for a demo or buy our AI Hunter! Follow us on Twitter: https://www.twitter.com/securityweekly Like us on Facebook: https://www.facebook.com/secweekly   Show Notes: https://securityweekly.com/psw770

Open source is the bedrock of most of the world's software today, so how to raise the floor on software quality across the industry? First, we need better tools to measure the trustworthiness of code based on objective measures, processes that encourage better security practices by developers, and tools and processes that encourage teamwork and shared responsibility for security. Several efforts are underway in major open source communities to address these issues. At the Open Source Security Foundation (OpenSSF), major companies, open source software maintainers, startup companies and government actors are working together to improve open source software supply chain security. Brian will share his view of this landscape, detail the work being done at the OpenSSF, show where those efforts are already bearing fruit, and demonstrate what you and your organization can (must!) do to participate in these efforts. Segment Resources: https://openssf.org/   Visit https://www.securityweekly.com/psw for all the latest episodes! Show Notes: https://securityweekly.com/psw770

Doc Searls and Simon Phipps talk with Brian Behlendorf, one of the original authors of Apache, about his new gig at the Open Source Security Foundation, plus the many challenges of decentralization. As well as the challenges of getting governments to care about open source. Another great discussion on FLOSS Weekly. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast Compiler - FLOSS newrelic.com/FLOSS

Doc Searls and Simon Phipps talk with Brian Behlendorf, one of the original authors of Apache, about his new gig at the Open Source Security Foundation, plus the many challenges of decentralization. As well as the challenges of getting governments to care about open source. Another great discussion on FLOSS Weekly. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast Compiler - FLOSS newrelic.com/FLOSS

Doc Searls and Simon Phipps talk with Brian Behlendorf, one of the original authors of Apache, about his new gig at the Open Source Security Foundation, plus the many challenges of decentralization. As well as the challenges of getting governments to care about open source. Another great discussion on FLOSS Weekly. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast Compiler - FLOSS newrelic.com/FLOSS

Doc Searls and Simon Phipps talk with Brian Behlendorf, one of the original authors of Apache, about his new gig at the Open Source Security Foundation, plus the many challenges of decentralization. As well as the challenges of getting governments to care about open source. Another great discussion on FLOSS Weekly. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: IRL Podcast Compiler - FLOSS newrelic.com/FLOSS

AUSTIN, TEX. —Everyone uses open source software — and it's become increasingly apparent that not nearly enough attention has been paid to the security of that software. In a survey released by The Linux Foundation and Synk at the foundation's Open Source Summit in Austin, Tex.,  this month, 41% of organizations said they aren't confident in the security of the open source software they use. At the Austin event, The New Stack's Makers podcast sat down with Brian Behlendorf, general manager of Open Source Security Foundation (OpenSSF), to talk about a new plan to attack the problem from multiple angles. He was interviewed for this On the Road edition of Makers by Heather Joslyn, features editor at The New Stack. Behlendorf, who has led OpenSSF since October and serves on the boards of the Electronic Frontier Foundation and Mozilla Foundation, cited the discovery of the Log4j vulnerabilities late in 2021, and other recent security “earthquakes” as a key turning points.“I think the software industry this year really woke up to not only the fact these earthquakes were happening,” he said, “and how it's getting more and more expensive to recover from them.” The Open Source Security Mobilization Plan sprung from an open source security summit in May. It identifies 10 areas that will be targeted for attention, according to the report published by OpenSSF and the Linux Foundation: Security education.Risk assessment.Digital signatures, such as though the open source Sigstore project.Memory safety.Incident response.Better scanning.Code audits.Data sharing.Improved software supply chains.Software bills of material (SBOMs) everywhere. The price tag for these initiatives over the initial two years is expected to total $150 million, Behlendorf told our Makers audience. The plan was sparked by queries from the White House about the various initiatives underway to improve open source software security — what they would cost, and the time frame the solution-builders had in mind. “We couldn't really answer that without being able to say, well, what would it take if we were to invest?” Behlendorf said. “Because most of the time we sit there, we wait for folks to show up and hope for the best.” The ultimate price tag, he said, was much lower than he expected it would be. Various member organizations within OpenSSF, he said, have pledged funding. “The 150 was really an estimate. And these plans are still being refined,” Behlendorf said. But by stating specific steps and their costs, he feels confident that interested parties will feel confident when it comes time to make good on those pledges. Listen to the podcast to get more details about the Open Source Security Mobilization Plan.

Brian Behlendorf came from a science and technology background. In fact, his parents met at IBM where his father was a Cobol programmer. During the 1980s, Brian was comfortable in front of a TRS 80 and a PC junior doing basic programming and term reports. He quickly found his way onto Usenet and participation on mailing lists around the band REM or the record label 4AD. This eventually turned into a dedicated mailing list focused on the rave scene in San Francisco. Through setting up the mailing list, he stood up an FTP server with DJ sets, which eventually became a gopher server, which eventually became a a web server that was dedicated to electronic music and the electronic music scene in the Bay Area. This was a time when you would only hear electronic music at certain events and not on the radio. Brian continued to go to school at UC Berkeley occasionally, but in January 1993, something else caught his attention. The first issue of https://www.wired.com/ (Wired Magazine) was published. From the Linux Foundation offices in New York City, this is The Untold Stories of Open Source. Each week in our podcast project on GitHub, we uncover the history and people behind the open source projects that are the foundation of technological innovation. If you work with open source, and you do whether you know it or not, you're in the right place. Mentioned in this episode: Pre-Roll - OpenSSF Day 2022 - Jennifer Bly Support for The Untold Stories of Open Source comes from the OpenSSF Project. Don't miss the first ever OpenSSF Day at Open Source Summit on June 20th in Austin. OpenSSF Day is included with your Open Source Summit registration. Reserve your spot at events.linux foundation.org.

Brian Behlendorf is the General Manager of the Open Source Security Foundation. Brian has dedicated his career to connecting and empowering the free software and open source community to both solve difficult technology problems and have a positive impact on society. From startup company founder, to advisor to the U.S. government, to non-profit board member and employee of the World Economic Forum, he's been at the forefront of the open source software revolution. Join hosts Luke Schantz and Joe Sepi as they get Brian's take on the latest open source software developments. As the recent Log4J vulnerability has shown, open source software is not immune to security breaches and attack. Brian shares his views on the Log4J scramble, his recent White House meetings on software security, the costs of security and threat mitigation, and future challenges and opportunities in open source software. Join us for a look back at Brian Behlendorf's unique career and see what's next for him and the movement he helped launch, this time on In the Open with Luke & Joe.Links:Brian Behlendorf bio: https://en.wikipedia.org/wiki/Brian_B...Open Source Foundations Must Work Together to Prevent the Next Log4Shell Scramble: https://openssf.org/blog/2021/12/16/o...Open Source @ IBM: https://www.ibm.com/opensource/IBM Open Source featured projects: https://www.ibm.com/opensource/open-p...____________________________________________Learn in-demand skills. Build with real code. Connect to a global development community: http://ibm.biz/IBMdeveloperYTSubscribe to see more developer content → https://www.youtube.com/user/develope...Follow IBM Developer on social:Twitter: https://twitter.com/IBMDeveloperFacebook: https://www.facebook.com/IBMDeveloper/LinkedIn: https://www.linkedin.com/showcase/ibm...More from IBM Developer:Community: https://developer.ibm.com/community/Blog: https://developer.ibm.com/blogs/Call for Code: https://developer.ibm.com/callforcode/#opensource#Developer#Coding#IntheOpen#IBMDeveloper

This week on DisrupTV, we interviewed Brian Behlendorf, General Manager for Blockchain, Healthcare and Identity at the Linux Foundation, Jennifer Briscoe, VP of Product Development at Oracle and Brian Fanzo, Speaker & Change Evangelist. DisrupTV is a weekly Web series with hosts R “Ray” Wang and Vala Afshar. The show airs live at 11:00 a.m. PT/ 2:00 p.m. ET every Friday. Brought to you by Constellation Executive Network: constellationr.com/CEN.

Chat with Vitalik Buterin, Co-founder Ethereum and Brian Behlendorf

Brian Behlendorf is the Executive Director of the Hyperledger project hosted by the Linux Foundation. He’s written and spoken extensively on open-source software development and communities. In 1999, he co-founded the Apache Software foundation, a non-profit that supports several open source project around key internet technologies. Brian has served on the board of the Mozilla foundation since 2003 and was CTO at the World economic forum. Hyperledger was started in 2015 by the Linux Foundation and hosts some of the most popular enterprise-grade distributed ledger platforms like Hyperledger Fabric, Besu, Indy, and Sawtooth. Brian's Twitter: https://twitter.com/brianbehlendorf Brian's Wikipedia page: https://en.wikipedia.org/wiki/Brian_Behlendorf Hyperledger Website: https://www.hyperledger.org/use Show Notes •Brian's background •When did you first learn about blockchain? •How do you compare the current blockchain revolution to the internet revolution of the 90s? •Linux Foundation involvement in healthcare •Launching Hyperledger •What excites you most about the Hyperledger network and its community? •Does the lack of a native cryptocurrency mean there's less incentivize for Hyperledger developers compared to other smart contract DLTs like Ethereum? Or is it a scaling advantage for Hyperledger? •How close are we to a global self-sovereign identity solution? Indy project •Future of identity •Selective disclosure •BBS+ signatures, •Can we expect real privacy and protection from government surveillance in the future? •WHO Vaccine cards historical insight •Public vs. Private DLT - how to choose the right level of openness for business applications? •How important is community and stakeholder governance when developing a DLT solutions? Philosophical/Personal •What do you believe in that most people would disagree with? •(Not to get political) how can technology be used to address drug taboos in our society? •In your view, what would it take for Bitcoin to lose it's #1 place in total network value (in USD)? •Will you be attending Burning Man this year? •Favorite book that has influenced you – The Making of the Atomic Bomb by Richard Rhodes •If you had to have micro chip implanted in your body, where would you want it to be implanted? •DAW (digital audio workstation) of choice – MIXX, OBS, Twitch •Is it fair to have an open network where people can join with equal voting rights without any previous investment or effort into a project? •Key Takeaways News Corner https://www.coindesk.com/microsoft-azure-service-blockchain-close Microsoft has decided to terminate its Azure-based blockchain-as-a-service platform. According to a recent blog post, Microsoft announced, they have been quietly informing customers on the best way to migrate their data to an alternative of their choosing by Sept. 10. Support for new deployments or member creations has also been discontinued. No official reason for their decision has been shared by the company. In late January 2016, Microsoft offered Azure's DevTest Labs so that Blockchain-related services and partners can decouple the Blockchain technology from virtual machines. Microsoft's short-term goal for the Azure BaaS was to make available a certified blockchain marketplace. The recommended migration destination is ConsenSys Quorum Blockchain Service. Users also could opt to self-manage their blockchains using Virtual Machines. Health Unchained Links Website: https://healthunchained.org Telegram: t.me/healthunchained Twitter: twitter.com/Healthunchaind

The safest way to return to full-capacity mass gatherings is to make sure attendees have been vaccinated. The right software could help, but there are some privacy and equity concerns. On Today's Show:New York recently launched a vaccine passport called the "Excelsior Pass." Brian Behlendorf, general manager of Blockchain Healthcare and Identity at the Linux Foundation of Public Health, talks about what it is, and how people in the open source community are advocating for systems like these to be linked, so people don't need multiple apps. Then, Albert Fox Cahn, founder and executive director of the Surveillance Technology Oversight Project (STOP) at the Urban Justice Center, a New York–based civil rights and privacy group, and a fellow at the Engelberg Center for Innovation Law & Policy at NYU School of Law shares concerns about privacy and the digital divide.

New York recently launched a vaccine passport called the "Excelsior Pass." Brian Behlendorf, general manager of Blockchain Healthcare and Identity at the Linux Foundation of Public Health, talks about what it is, and how people in the open source community are advocating for systems like these to be linked, so people don't need multiple apps. Then, Albert Fox Cahn, founder and executive director of the Surveillance Technology Oversight Project (STOP) at the Urban Justice Center, a New York–based civil rights and privacy group, and a fellow at the Engelberg Center for Innovation Law & Policy at NYU School of Law shares concerns about privacy and the digital divide.

This panel, from a panel for the fifth anniversary of Hyperledger, features Rob Palatnick, managing director of global head of technology research and innovation at the DTCC and chairman of the Hyperledger board, Matthieu Saint Olive, Codefi payments product manager and CBDC advisor at ConsenSys, and Robert Bench, assistant vice president at the Federal Reserve Bank of Boston. In this discussion on the current outlook on central bank digital currencies (CBDCs), they cover:  what main problems CBDCs can solve whether CBDCs should be open sourced why building a new technology for CBDCs is preferred over using existing tech how concerns over CBDCs and their privacy implications differ across countries what possible pain points or opportunities CBDCs pose for central banks whether CBDCs should be blockchain-based to what extent CBDCs will be distributed and open networks, and whether fees would be charged for transactions how central banks are thinking about methods of adoption, like whether they will bank directly with retail customers or still use commercial banks  how developers balance the drawbacks and benefits of blockchain-based CBDCs with different stakeholders whether stable coins will be replaced by or coexist with CBDCs and what the future holds for the continued development of CBDCs   Thank you to our sponsors! Crypto.com: http://crypto.com 1inch: http://1inch.exchange    Episode links:  Rob Palatnick: https://www.dtcc.com/our-experts/robert-palatnick Brian Behlendorf: https://twitter.com/brianbehlendorf?lang=en  Matthieu Saint Olive: https://twitter.com/msaintolive?lang=en  Robert Bench: https://www.bostonfed.org/home/people/bank/robert-bench.aspx

This panel, from a panel for the fifth anniversary of Hyperledger, features Rob Palatnick, managing director of global head of technology research and innovation at the DTCC and chairman of the Hyperledger board, Matthieu Saint Olive, Codefi payments product manager and CBDC advisor at ConsenSys, and Robert Bench, assistant vice president at the Federal Reserve Bank of Boston. In this discussion on the current outlook on central bank digital currencies (CBDCs), they cover:  what main problems CBDCs can solve whether CBDCs should be open sourced why building a new technology for CBDCs is preferred over using existing tech how concerns over CBDCs and their privacy implications differ across countries what possible pain points or opportunities CBDCs pose for central banks whether CBDCs should be blockchain-based to what extent CBDCs will be distributed and open networks, and whether fees would be charged for transactions how central banks are thinking about methods of adoption, like whether they will bank directly with retail customers or still use commercial banks  how developers balance the drawbacks and benefits of blockchain-based CBDCs with different stakeholders whether stable coins will be replaced by or coexist with CBDCs and what the future holds for the continued development of CBDCs   Thank you to our sponsors! Crypto.com: http://crypto.com 1inch: http://1inch.exchange    Episode links:  Rob Palatnick: https://www.dtcc.com/our-experts/robert-palatnick Brian Behlendorf: https://twitter.com/brianbehlendorf?lang=en  Matthieu Saint Olive: https://twitter.com/msaintolive?lang=en  Robert Bench: https://www.bostonfed.org/home/people/bank/robert-bench.aspx

We read FreeBSD’s 3rd quarter status report, OpenZFS 2.0, adding check-hash checks in UFS filesystem, OpenSSL 3.0 /dev/crypto issues on FreeBSD, and more. NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) Headlines 3rd Quarter FreeBSD Report (https://www.freebsd.org/news/status/report-2020-07-2020-09.html) The call for submissions for the 4th Quarter is out (https://lists.freebsd.org/pipermail/freebsd-quarterly-calls/2020/000007.html) OpenZFS 2.0 (https://arstechnica.com/gadgets/2020/12/openzfs-2-0-release-unifies-linux-bsd-and-adds-tons-of-new-features/) This Monday, ZFS on Linux lead developer Brian Behlendorf published the OpenZFS 2.0.0 release to GitHub. Along with quite a lot of new features, the announcement brings an end to the former distinction between "ZFS on Linux" and ZFS elsewhere (for example, on FreeBSD). This move has been a long time coming—the FreeBSD community laid out its side of the roadmap two years ago—but this is the release that makes it official. News Roundup Revision 367034 (https://svnweb.freebsd.org/changeset/base/367034) Various new check-hash checks have been added to the UFS filesystem over various major releases. Superblock check hashes were added for the 12 release and cylinder-group and inode check hashes will appear in the 13 release. OpenSSL 3.0 /dev/crypto issues on FreeBSD (https://rubenerd.com/openssl-3-written-to-break-on-freebsd/) So, just learned that the OpenSSL devs decided to break /dev/crypto on FreeBSD. OS108-9.1 XFCE amd64 released (https://forums.os108.org/d/32-os108-91-xfce-amd64-released) OS108 is a fast, open and Secure Desktop Operating System built on top of NetBSD. > Installing OS108 to your hard drive is done by using the sysinst utility, the process is basically the same as installing NetBSD itself. Please refer to the NetBSD guide for installation details, http://www.netbsd.org/docs/guide/en/part-install.html Installation Video (https://youtu.be/cgAeY21gXR4) *** Beastie Bits OpenBGPD 6.8p1 portable: released Nov 5th, 2020 (http://www.openbgpd.org/ftp.html) IRC Awk Bot (http://kflu.github.io/2020/08/15/2020-08-15-awk-irc-bot/) Docker on FreeBSD using bhyve and sshfs (https://www.youtube.com/watch?v=ZVkJZJEdZNY) The UNIX Command Language (1976) (https://github.com/susam/tucl) *** Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions santi - openrc (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/380/feedback/santi%20-%20openrc.md) trond - python2 and mailman (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/380/feedback/trond%20-%20python2%20and%20mailmane%20and%20sshfs) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Glaubt man Brian Behlendorf, einer der führenden Entwickler, dann ist die Cryptotechnologie inzwischen in den Unternehmen angekommen. Tokenisierung als Konzept und Digitale Assets gehörten zunehmend zum Alltag, sagte er auf dem diesjährigen Websummit. Institutionelle Investoren strömen bereits in Scharen zu Bitcoin-Investments, haben Strategen von JPMorgan jetzt festgestellt. Nach ihrer Einschätzung könnte dieser Trend sogar längerfristig Abwärtsdruck auf Gold als "sicherer Hafen" ausüben.Die Investmentbanker stellten fest, dass der Bitcoin-Trust des Digital Asset Managers Grayscale in den letzten zwei Monaten einen Zufluss von fast 2 Milliarden Dollar verzeichnete, während die Gold-ETFs Abflüsse von über 7 Milliarden Dollar verzeichneten. Grund genug, die Hintergründe zu erfragen: Victor von Wachter, Anlageexperte bei der Asset Management-Beratung 21e6, hat eine klare Meinung, woher das steigende Interesse kommt, warnt private Anleger aber zugleich vor dem unvorbereiteten Einstieg in den Crypto-Markt.Support the show (https://www.patreon.com/kommponisten)

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Hyperledger is an open-source community focused on developing a suite of stable frameworks, tools, and libraries for enterprise-grade blockchain deployments. Doc Searls and Simon Phipps talk with Brian Behlendorf, the executive director of Hyperledger. They discuss the growth of Hyperledger since the last time Brian was on the show. Open source started with operating systems 20 years ago, but now it is stretching into different domains. One of those ways is in public health. They discuss the Linux Foundation of public health, which sustains open-source software to help public health authorities (PHAs) combat COVID-19 and future epidemics. They also ask Brian about how the Mozilla Foundation Model compares to Linux Foundation. Hosts: Doc Searls and Simon Phipps Guest: Brian Behlendorf Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Sponsors: WWT.COM/TWIT expressvpn.com/floss

Chris Ferris is an IBM Fellow and CTO for Open Technology and Governing Board Member of Hyperledger. In this exciting podcast we discuss "is open source the future of blockchain"? Open source has increasingly converted enterprises to both use its technology and contribute to its code base. In a similar manner open source in the form of its open governance approach has some important lessons for blockchain networks to analyse and adopt. Have a listen and let us know if you think open source is the future of blockchain?   What is blockchain? At its essence a blockchain is an audit log of successive records where each successive record in that audit log is cryptographically bound to all of the log entries before it. Blockchain can be used as a means of ensuring that there hasn't been any tampering of the contents of that audit log. There are other technologies that are built out around it to give it purpose.   What is open source? The formal definition of open source is that it's software whose source code is made freely available and can be redistributed and it can be modified. The Open Source Initiative has ten dimensions defining what is open source and the terms for its distribution: Free redistribution Source code must be included in program Derived works can be modified and freely redistributed Integrity of the author’s source code No discrimination against persons or groups No discrimination against fields of endeavour Distribution of license License must not be specific to a product License must not restrict other software License must be technology-neutral   History of open source & why are enterprises contributors to open source In 1983 open source was known as the “free software” movement with Microsoft labelling it as the “enemy”. In 1998 “free software” evolved into “open source”. Microsoft wasn’t the enemy anymore and it along with Red Hat, Intel, Alibaba Group, Google, Facebook and of course IBM became some of the biggest enterprise contributors to open source. What is important to understand is that whilst open source is free many firms such as IBM, Red Hat or Microsoft offer services to support the software or build commercialised versions of open source software. Brian Behlendorf, Executive Director at Hyperledger was also involved in the original formation of the Apache Software Foundation. At the foundation they have an expression called Do-ocracy, which is where you roll up your sleeves, you get down and you do the work. From an open source perspective, even from a corporate or an enterprise engagement in open source perspective it really is about the notion of do-ocracy. Enterprises like IBM, Microsoft, Red Hat and others get involved in open source projects because they’re of strategic interest and/or they’re using that technology as a function of a platform, offering or tools they they’re selling. Their contribution to open source projects is out of self-interest. Chris gives the example that if IBM is using Kubernetes to power the container orchestration within the IBM Cloud, “..well, then we would be silly not to contribute to Kubernetes to keep it, you know, functioning to add new features and capabilities, improve the performance, and so forth”.   Hyperledger & the Linux Foundation   Jerry Cuomo, another IBM Fellow had been working on a skunkswork project internally around building blockchain technology for enterprises. Jerry discussed with Chris on whether or not to open source this blockchain enterprise technology or to have it as proprietary. Chris stated to Jerry “.. this isn't going to be successful if it's just proprietary IBM technology, how are we going to get other companies to buy into an IBM only capability? I said, so I think it really needs to be open source and it needs to be open source under an open governance model” Chris brought a proposal to Jim Zemlin,

China's development of blockchain technology may result in it 'leapfrogging' over other countries' information systems to create a "global blockchain with Chinese characteristics," according to Brian Behlendorf, executive director of Hyperledger.

China's development of blockchain technology may result in it 'leapfrogging' over other countries' information systems to create a "global blockchain with Chinese characteristics," according to Brian Behlendorf, executive director of Hyperledger.

Brian Behlendorf, Executive Director of the Hyperledger Foundation, gives an overview of The Hyperledger Greenhouse, explaining the different distributed ledgers within the Hyperledger community and how each architecture is being used for different blockchain projects.  Brian also goes into detail about open source and its impact on blockchain technology, noting that his interest of blockchain came about due to his views on open source standards. He also comments on Hyperledger Besu and how it taps into the ethereum public blockchain.   Full Show Notes At: https://thecryptochick.io/023 Show Edited By: Aaron The Tech (http://aaronthe.tech) See omnystudio.com/listener for privacy information.

Simon and Colin are back this week to talk about the latest and greatest news in blockchain, including: Libra fallout continues, Polkadot and tethery’licious volume! First up, we take a look at how central banks plan to create digital currencies, and it recieves backing! Augustin Castens, The GM of the Bank of International Settlements, has said that Global central banks may have to issue their own digital currencies sooner than expected! When asked about Libra, Castens said “The issue is how will the currency be used? Will there to be a discovery of information or data that can be used in credit provision and how will data privacy be protected?". A couple of months ago, the conversation was more around how you don't need central bank digital currencies, has libra changed the tone of the conversation? (01:13) Next we talk about the 5 Reasons why Facebook’s new cryptocurrency ‘Libra’ is bad news for Africa! The reasons stated are as following: - Libra Coin is Digital Colonization by Proxy - Libra Coin Is a Threat to African Central Bank and Monetary Policy - Libracoin is Threat to African Sovereignty and the African People - Africa Will Give Up Control Over It’s Digital Economy to Libra coin and Facebook - Big Brother Africa Colin argues that one big caveat in this article is that Africa is not one big country, and a lot of statements in this article are rather generalising. Simon argues that this article is written looking through a very dystopian lens. Could Libra be considered dystopian? (08:44) Other stories include: * UK crypto scene set for boost as London firm poised for FCA approval (14:11) * Globacap Launches FCA-Regulated Digital Security Offering Platform (18:07) * Ethereum Co-Founder’s Polkadot Closes Token Sale, Claims $1.2 Billion Valuation (23:33) * Wha-Tether could be going on with the bitcoin price? (30:27) We also have another brilliant interview for you, this week from Brian Behlendorf, Executive Director of the Hyperledger Project! We also have a great Tweet of the Week from @APompliano, about all the exciting things that's happened in crypto this week. All this and so much more on this week's episode of Blockchain Insider. And why not send us your best tweets? See if you can get a shout out on the show! ​ We hope you enjoy the show and, as ever, don't forget to subscribe! ​ Want to join the conversation on all the topics discussed? Tweet the show @bchaininsider and if you really love the show, please leave us a review on iTunes. ​ This week's episode of Blockchain Insider was produced by Laura Watkins and Petrit Berisha. Edited by Alex Woodhouse. Special Guest: Brian Behlendorf.

Part of the Linux Foundation, Hyperledger is an open source initiative to build blockchain solutions across industries. Executive director Brian Behlendorf discusses what blockchain is, and how this “distributed ledger” model applies to healthcare challenges both now and in the future. Recorded at HIMSS 2019.   In episode: Hyperledger website

An Open Source pioneer, Brian Behlendorf now leads the effort to
 build the infrastructure for trust as a service. In the past he helped build the foundations of the Web with the Apache Foundation and brought Open Source to the enterprise with Collab.net. At The Interval he’ll discuss his current work leading Hyperledger at the Linux Foundation to unlock blockchain’s potential beyond cryptocurrency. Brian Behlendorf is Executive Director for Hyperledger, a project of the Linux Foundation. Hyperledger is an open source collaborative effort created to advance cross-industry blockchain technologies. Previously he was the primary developer of the Apache Web server, the most popular web server software on the Internet, and a founding member of the Apache Software Foundation. He was the founding CTO of CollabNet and CTO of the World Economic Forum. Most recently, Behlendorf was a managing director at Mithril Capital Management LLC, a global technology investment firm. He is a long-serving board member of the Mozilla Foundation and the Electronic Frontier Foundation.

If you have any questions about whether or not you should be on the blockchain - Brian Behlendorf, Hyperledger's CEO, breaks down an approach and a framework on how you start looking at this. He shares some of the projects that they are working on to give us a practical example of how Hyperledger is solving real problems.

The future of ZFS in FreeBSD, we pick highlights from the FreeBSD quarterly status report, flying with the raven, modern KDE on FreeBSD, many ways to launch FreeBSD in EC2, GOG installers on NetBSD, and more. Headlines The future of ZFS in FreeBSD The sources for FreeBSD’s ZFS support are currently taken directly from Illumos with local ifdefs to support the peculiarities of FreeBSD where the Solaris Portability Layer (SPL) shims fall short. FreeBSD has regularly pulled changes from Illumos and tried to push back any bug fixes and new features done in the context of FreeBSD. In the past few years the vast majority of new development in ZFS has taken place in DelphixOS and zfsonlinux (ZoL). Earlier this year Delphix announced that they will be moving to ZoL: https://www.delphix.com/blog/kickoff-future-eko-2018 This shift means that there will be little to no net new development of Illumos. While working through the git history of ZoL I have also discovered that many races and locking bugs have been fixed in ZoL and never made it back to Illumos and thus FreeBSD. This state of affairs has led to a general agreement among the stakeholders that I have spoken to that it makes sense to rebase FreeBSD’s ZFS on ZoL. Brian Behlendorf has graciously encouraged me to add FreeBSD support directly to ZoL https://github.com/zfsonfreebsd/ZoF so that we might all have a single shared code base. A port for ZoF can be found at https://github.com/miwi-fbsd/zof-port Before it can be committed some additional functionality needs to be added to the FreeBSD opencrypto framework. These can be found at https://reviews.freebsd.org/D18520 This port will provide FreeBSD users with multi modifier protection, project quotas, encrypted datasets, allocation classes, vectorized raidz, vectorized checksums, and various command line improvements. FreeBSD Quarterly Status Update With FreeBSD having gone all the way to 12, it is perhaps useful to take a look back at all the things that have been accomplished, in terms of many visible changes, as well as all the things that happen behind the scenes to ensure that FreeBSD continues to offer an alternative in both design, implementation, and execution. The things you can look forward to reading about are too numerous to summarize, but cover just about everything from finalizing releases, administrative work, optimizations and depessimizations, features added and fixed, and many areas of improvement that might just surprise you a little. Please have a cup of coffee, tea, hot cocoa, or other beverage of choice, and enjoy this culmulative set of reports covering everything that’s been done since October, 2017. —Daniel Ebdrup News Roundup One year of flying with the Raven: Ready for the Desktop? It has been a little over one year now that I’m with the Ravenports project. Time to reflect my involvement, my expectations and hopes. Ravenports Ravenports is a universal packaging framework for *nix operating systems. For the user it provides easy access to binary packages of common software for multiple platforms. It has been the long-lasting champion on Repology’s top 10 repositories regarding package freshness (rarely dropping below 96 percent while all other projects keep below 90!). For the porter it offers a well-designed and elegant means of writing cross-platform buildsheets that allow building the same version of the software with (completely or mostly) the same compile-time configuration on different operating systems or distributions. And for the developer it means a real-world project that’s written in modern Ada (ravenadm) and C (pkg) – as well as some Perl for support scripts and make. Things feel very optimized and fast. Not being a programmer though, I cannot really say anything about the actual code and thus leave it to the interested reader’s judgement. Modern KDE on FreeBSD New stuff in the official FreeBSD repositories! The X11 team has landed a newer version of libinput, opening up the way for KDE Plasma 5.14 in ports. That’s a pretty big update and it may frighten people with a new wallpaper. What this means is that the graphical stack is once again on-par with what Plasma upstream expects, and we can get back to chasing releases as soon as they happen, rather than gnashing our teeth at missing dependencies. The KDE-FreeBSD CI servers are in the process of being upgraded to 12-STABLE, and we’re integrating with the new experimental CI systems as well. This means we are chasing sensibly-modern systems (13-CURRENT is out of scope). The many ways to launch FreeBSD in EC2 Talking to FreeBSD users recently, I became aware that while I’ve created a lot of tools, I haven’t done a very good job of explaining how, and more importantly when to use them. So for all of the EC2-curious FreeBSD users out there: Here are the many ways to launch and configure FreeBSD in EC2 — ranging from the simplest to the most complicated (but most powerful): Launch FreeBSD and SSH in Launch FreeBSD and provide user-data Use the AMI Builder to create a customized FreeBSD AMI Build a FreeBSD AMI from a modified FreeBSD source tree Build your own disk image I hope I’ve provided tools which help you to run FreeBSD in EC2, no matter how common or unusual your needs are. If you find my work useful, please consider supporting my work in this area; while this is both something I enjoy working on and something which is useful for my day job (Tarsnap, my online backup service), having support would make it easier for me to prioritize FreeBSD/EC2 issues over other projects. Using the GOG.com installers for Linux, on NetBSD GOG.com prefers that you use their GOG Galaxy desktop app to download, install and manage all of your GOG games. But customers always have the option to install the game on their own terms, with a platform-specific installer. GOG offers these installers for Mac, Windows and/or Linux, depending on which platforms the game is available for. The installers truly are platform-specific: macOS games are distributed in a standard .pkg Windows games are distributed in a setup wizard .exe Linux games are distributed in a goofy shell archive Of course, none of those are NetBSD. So, if I wanted to even attempt to play a game distributed by GOG.com on NetBSD, which one should I pick? The obvious choice is the Linux installer, since Linux is the most similar to NetBSD, right? Au contraire! In practice, I found that it is easier to download the Windows installer. Here’s what I mean. For example, I ported the open source version of Aquaria to pkgsrc, but that package is only the game’s engine, not the multimedia data. The multimedia data is still copyrighted. Therefore, you need to get it from somewhere else. GOG is usually a good choice, because they distribute their games without DRM. And as mentioned earlier, picking the Linux installer seemed like a natural choice. Now, actually PLAYING the games on NetBSD is a separate matter entirely. The game I’ve got here, though, my current obsession Pyre, is built with MonoGame and therefore could theoretically work on NetBSD, too, with the help of a library called FNA and a script for OpenBSD called fnaify. I do hope to create a pkgsrc package for FNA and port the fnaify script to NetBSD at some point. Beastie Bits Software as a Reflection of Values With Bryan Cantrill Collection of bmc talks, updated 2018 wump: incorrect wumpus movement probability Debugging Rust with VSCode on FreeBSD SMB/CIFS on FreeBSD BSD Tattoo pkgsrc-2018Q4 branch announcement toying with wireguard on openbsd new USB audio class v2.0 driver Todd Mortimer Removing ROP Gadgets from OpenBSD EuroBSDCon 2018 OpenBSD 6.5 release page is online shell access to historical Unix versions in your browser Feedback/Questions Brad - ZFS Features and Upgrades Andre - Splitting ZFS array Michael - Priority/nice value for Jails? Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

Most observers of the ecosystem will probably agree that 2015-2017 were the years of the enterprise blockchain. It was during that time that many startups catering to enterprise were founded and funded, including Monax and Stratumn (where Brian and Sebastien previously worked). For the permissioned blockchain camp, adoption would come in the form of enterprise use cases, arguing that public networks carried too much risk, and lacked needed features like privacy. While much of the hype has subsided, large companies in every sector are forming consortia and leveraging blockchain to provide better process traceability and transparency, and reduce their reliance on third parties. We’re joined by Brian Behlendorf, Executive Director of Hyperledger. When Brian was last on the show, he had recently started his role at the Linux Foundation. Now, two years later, Hyperledger has gone from a nascent project to a mature ecosystem of technologies with hundreds of members. With dozens of networks in production, and backed by companies like IBM, Hyperleger is the most widely used blockchain technology for permissioned networks. Topics covered in this episode: The most important developments in Hyperledger in the last two years Hyperledger’s family of technologies Production networks on Hyperledger How Hyperledger Fabric differs from Tendermint and Ethereum The evolution of the enterprise blockchain ecosystem The separation between the permissioned and public blockchain ecosystems Industry use cases for Hyperledger Fabric Brian’s skepticism about ICOs and tokens The growing Hyperledger community and upcoming Global Forum in Basel this December Episode links: Hyperledger website Hyperledger Global Forum http://sdxcentral.com Unbounded - To Network with Networks Pittsburgh, Cincinnati, Chicago and St. Louis Railroad - Wikipedia Thank you to our sponsors for their support: Simplify your hiring process & access the best blockchain talent . Get a $1,000 credit on your first hire at toptal.com/epicenter. This episode is hosted by Brian Fabian Crain and Sébastien Couture. Show notes and listening options: epicenter.tv/262

On a special episode of Late Confirmation, we visit the Concordia Annual Summit in New York City, where a broad range of thinkers and creators from different fields gather alongside the UN General Assembly. In this episode, we sit down with four notable attendees from the blockchain sphere and ask them each one question: Where is blockchain tech on the hype cycle?The Gartner hype cycle, for those who don’t know, tracks the expectations of a new technology over time. Developing technology can hit the Peak of Inflated Expectations before falling into the Trough of Disillusionment, from which –– if successful –– it will emerge onto the Slope of Enlightenment. As a subjective measuring tool, the hype cycle can be useful thought experiment for thinking about discussions of blockchain technology.Our interviewees in this episode include Hyperledger’s Brian Behlendorf, attorney Preston Byrne, Microsoft’s Blockchain Engineering team Project Manager Yorke Rhodes, and Jalak Jobanputra, founding partner of Future/Perfect Ventures.Thanks to our sponsors!Said Business School, University of OxfordOxford Fintech ProgrammeOxford Blockchain Strategy ProgrammeLate Confirmation is a CoinDesk production made in collaboration with The Podglomerate.For more information, visit www.CoinDesk.com

Insight into TrueOS and Trident, stop evildoers with pf-badhost, Flashback to FreeBSDcon ‘99, OpenBSD’s measures against TLBleed, play Morrowind on OpenBSD in 5 steps, DragonflyBSD developers shocked at Threadripper performance, and more. ##Headlines An Insight into the Future of TrueOS BSD and Project Trident Last month, TrueOS announced that they would be spinning off their desktop offering. The team behind the new project, named Project Trident, have been working furiously towards their first release. They did take a few minutes to answer some of our question about Project Trident and TrueOS. I would like to thank JT and Ken for taking the time to compile these answers. It’s FOSS: What is Project Trident? Project Trident: Project Trident is the continuation of the TrueOS Desktop. Essentially, it is the continuation of the primary “TrueOS software” that people have been using for the past 2 years. The continuing evolution of the entire TrueOS project has reached a stage where it became necessary to reorganize the project. To understand this change, it is important to know the history of the TrueOS project. Originally, Kris Moore created PC-BSD. This was a Desktop release of FreeBSD focused on providing a simple and user-friendly graphical experience for FreeBSD. PC-BSD grew and matured over many years. During the evolution of PC-BSD, many users began asking for a server focused version of the software. Kris agreed, and TrueOS was born as a scaled down server version of PC-BSD. In late 2016, more contributors and growth resulted in significant changes to the PC-BSD codebase. Because the new development was so markedly different from the original PC-BSD design, it was decided to rebrand the project. TrueOS was chosen as the name for this new direction for PC-BSD as the project had grown beyond providing only a graphical front to FreeBSD and was beginning to make fundamental changes to the FreeBSD operating system. One of these changes was moving PC-BSD from being based on each FreeBSD Release to TrueOS being based on the active and less outdated FreeBSD Current. Other major changes are using OpenRC for service management and being more aggressive about addressing long-standing issues with the FreeBSD release process. TrueOS moved toward a rolling release cycle, twice a year, which tested and merged FreeBSD changes directly from the developer instead of waiting months or even years for the FreeBSD review process to finish. TrueOS also deprecated and removed obsolete technology much more regularly. As the TrueOS Project grew, the developers found these changes were needed by other FreeBSD-based projects. These projects began expressing interest in using TrueOS rather than FreeBSD as the base for their project. This demonstrated that TrueOS needed to again evolve into a distribution framework for any BSD project to use. This allows port maintainers and source developers from any BSD project to pool their resources and use the same source repositories while allowing every distribution to still customize, build, and release their own self-contained project. The result is a natural split of the traditional TrueOS team. There were now naturally two teams in the TrueOS project: those working on the build infrastructure and FreeBSD enhancements – the “core” part of the project, and those working on end-user experience and utility – the “desktop” part of the project. When the decision was made to formally split the projects, the obvious question that arose was what to call the “Desktop” project. As TrueOS was already positioned to be a BSD distribution platform, the developers agreed the desktop side should pick a new name. There were other considerations too, one notable being that we were concerned that if we continued to call the desktop project “TrueOS Desktop”, it would prevent people from considering TrueOS as the basis for their distribution because of misconceptions that TrueOS was a desktop-focused OS. It also helps to “level the playing field” for other desktop distributions like GhostBSD so that TrueOS is not viewed as having a single “blessed” desktop version. It’s FOSS: What features will TrueOS add to the FreeBSD base? Project Trident: TrueOS has already added a number of features to FreeBSD: OpenRC replaces rc.d for service management LibreSSL in base Root NSS certificates out-of-box Scriptable installations (pc-sysinstall) The full list of changes can be seen on the TrueOS repository (https://github.com/trueos/trueos/blob/trueos-master/README.md). This list does change quite regularly as FreeBSD development itself changes. It’s FOSS: I understand that TrueOS will have a new feature that will make creating a desktop spin of TrueOS very easy. Could you explain that new feature? Project Trident: Historically, one of the biggest hurdles for creating a desktop version of FreeBSD is that the build options for packages are tuned for servers rather than desktops. This means a desktop distribution cannot use the pre-built packages from FreeBSD and must build, use, and maintain a custom package repository. Maintaining a fork of the FreeBSD ports tree is no trivial task. TrueOS has created a full distribution framework so now all it takes to create a custom build of FreeBSD is a single JSON manifest file. There is now a single “source of truth” for the source and ports repositories that is maintained by the TrueOS team and regularly tagged with “stable” build markers. All projects can use this framework, which makes updates trivial. It’s FOSS: Do you think that the new focus of TrueOS will lead to the creation of more desktop-centered BSDs? Project Trident: That is the hope. Historically, creating a desktop-centered BSD has required a lot of specialized knowledge. Not only do most people not have this knowledge, but many do not even know what they need to learn until they start troubleshooting. TrueOS is trying to drastically simplify this process to enable the wider Open Source community to experiment, contribute, and enjoy BSD-based projects. It’s FOSS: What is going to happen to TrueOS Pico? Will Project Trident have ARM support? Project Trident: Project Trident will be dependent on TrueOS for ARM support. The developers have talked about the possibility of supporting ARM64 and RISC-V architectures, but it is not possible at the current time. If more Open Source contributors want to help develop ARM and RISC-V support, the TrueOS project is definitely willing to help test and integrate that code. It’s FOSS: What does this change (splitting Trus OS into Project Trident) mean for the Lumina desktop environment? Project Trident: Long-term, almost nothing. Lumina is still the desktop environment for Project Trident and will continue to be developed and enhanced alongside Project Trident just as it was for TrueOS. Short-term, we will be delaying the release of Lumina 2.0 and will release an updated version of the 1.x branch (1.5.0) instead. This is simply due to all the extra overhead to get Project Trident up and running. When things settle down into a rhythm, the development of Lumina will pick up once again. It’s FOSS: Are you planning on including any desktop environments besides Lumina? Project Trident: While Lumina is included by default, all of the other popular desktop environments will be available in the package repo exactly as they had been before. It’s FOSS: Any plans to include Steam to increase the userbase? Project Trident: Steam is still unavailable natively on FreeBSD, so we do not have any plans to ship it out of the box currently. In the meantime, we highly recommend installing the Windows version of Steam through the PlayOnBSD utility. It’s FOSS: What will happen to the AppCafe? Project Trident: The AppCafe is the name of the graphical interface for the “pkg” utility integrated into the SysAdm client created by TrueOS. This hasn’t changed. SysAdm, the graphical client, and by extension AppCafe are still available for all TrueOS-based distributions to use. It’s FOSS: Does Project Trident have any corporate sponsors lined up? If not, would you be open to it or would you prefer that it be community supported? Project Trident: iXsystems is the first corporate sponsor of Project Trident and we are always open to other sponsorships as well. We would prefer smaller individual contributions from the community, but we understand that larger project needs or special-purpose goals are much more difficult to achieve without allowing larger corporate sponsorships as well. In either case, Project Trident is always looking out for the best interests of the community and will not allow intrusive or harmful code to enter the project even if a company or individual tries to make that code part of a sponsorship deal. It’s FOSS: BSD always seems to be lagging in terms of support for newer devices. Will TrueOS be able to remedy that with a quicker release cycle? Project Trident: Yes! That was a primary reason for TrueOS to start tracking the CURRENT branch of FreeBSD in 2016. This allows for the changes that FreeBSD developers are making, including new hardware support, to be available much sooner than if we followed the FreeBSD release cycle. It’s FOSS: Do you have any idea when Project Trident will have its first release? Project Trident: Right now we are targeting a late August release date. This is because Project Trident is “kicking the wheels” on the new TrueOS distribution system. We want to ensure everything is working smoothly before we release. Going forward, we plan on having regular package updates every week or two for the end-user packages and a new release of Trident with an updated OS version every 6 months. This will follow the TrueOS release schedule with a small time offset. ###pf-badhost: Stop the evil doers in their tracks! pf-badhost is a simple, easy to use badhost blocker that uses the power of the pf firewall to block many of the internet’s biggest irritants. Annoyances such as ssh bruteforcers are largely eliminated. Shodan scans and bots looking for webservers to abuse are stopped dead in their tracks. When used to filter outbound traffic, pf-badhost blocks many seedy, spooky malware containing and/or compromised webhosts. Filtering performance is exceptional, as the badhost list is stored in a pf table. To quote the OpenBSD FAQ page regarding tables: “the lookup time on a table holding 50,000 addresses is only slightly more than for one holding 50 addresses.” pf-badhost is simple and powerful. The blocklists are pulled from quality, trusted sources. The ‘Firehol’, ‘Emerging Threats’ and ‘Binary Defense’ block lists are used as they are popular, regularly updated lists of the internet’s most egregious offenders. The pf-badhost.sh script can easily be expanded to use additional or alternate blocklists. pf-badhost works best when used in conjunction with unbound-adblock for the ultimate badhost blocking. Notes: If you are trying to run pf-badhost on a LAN or are using NAT, you will want to add a rule to your pf.conf appearing BEFORE the pf-badhost rules allowing traffic to and from your local subnet so that you can still access your gateway and any DNS servers. Conversely, adding a line to pf-badhost.sh that removes your subnet range from the table should also work. Just make sure you choose a subnet range / CIDR block that is actually in the list. 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8 are the most common home/office subnet ranges. DigitalOcean https://do.co/bsdnow ###FLASHBACK: FreeBSDCon’99: Fans of Linux’s lesser-known sibling gather for the first time FreeBSD, a port of BSD Unix to Intel, has been around almost as long as Linux has – but without the media hype. Its developer and user community recently got a chance to get together for the first time, and they did it in the city where BSD – the Berkeley Software Distribution – was born some 25 years ago. October 17, 1999 marked a milestone in the history of FreeBSD – the first FreeBSD conference was held in the city where it all began, Berkeley, CA. Over 300 developers, users, and interested parties attended from around the globe. This was easily 50 percent more people than the conference organizers had expected. This first conference was meant to be a gathering mostly for developers and FreeBSD advocates. The turnout was surprisingly (and gratifyingly) large. In fact, attendance exceeded expectations so much that, for instance, Kirk McKusick had to add a second, identical tutorial on FreeBSD internals, because it was impossible for everyone to attend the first! But for a first-ever conference, I was impressed by how smoothly everything seemed to go. Sessions started on time, and the sessions I attended were well-run; nothing seemed to be too cold, dark, loud, late, or off-center. Of course, the best part about a conference such as this one is the opportunity to meet with other people who share similar interests. Lunches and breaks were a good time to meet people, as was the Tuesday night beer bash. The Wednesday night reception was of a type unusual for the technical conferences I usually attend – a three-hour Hornblower dinner cruise on San Francisco Bay. Not only did we all enjoy excellent food and company, but we all got to go up on deck and watch the lights of San Francisco and Berkeley as we drifted by. Although it’s nice when a conference attracts thousands of attendees, there are some things that can only be done with smaller groups of people; this was one of them. In short, this was a tiny conference, but a well-run one. Sessions Although it was a relatively small conference, the number and quality of the sessions belied the size. Each of the three days of the conference featured a different keynote speaker. In addition to Jordan Hubbard, Jeremy Allison spoke on “Samba Futures” on day two, and Brian Behlendorf gave a talk on “FreeBSD and Apache: A Perfect Combo” to start off the third day. The conference sessions themselves were divided into six tracks: advocacy, business, development, networking, security, and panels. The panels track featured three different panels, made up of three different slices of the community: the FreeBSD core team, a press panel, and a prominent user panel with representatives from such prominent commercial users as Yahoo! and USWest. I was especially interested in Apple Computer’s talk in the development track. Wilfredo Sanchez, technical lead for open source projects at Apple (no, that’s not an oxymoron!) spoke about Apple’s Darwin project, the company’s operating system road map, and the role of BSD (and, specifically, FreeBSD) in Apple’s plans. Apple and Unix have had a long and uneasy history, from the Lisa through the A/UX project to today. Personally, I’m very optimistic about the chances for the Darwin project to succeed. Apple’s core OS kernel team has chosen FreeBSD as its reference platform. I’m looking forward to what this partnership will bring to both sides. Other development track sessions included in-depth tutorials on writing device drivers, basics of the Vinum Volume Manager, Fibre Channel, development models (the open repository model), and the FreeBSD Documentation Project (FDP). If you’re interested in contributing to the FreeBSD project, the FDP is a good place to start. Advocacy sessions included “How One Person Can Make a Difference” (a timeless topic that would find a home at any technical conference!) and “Starting and Managing A User Group” (trials and tribulations as well as rewards). The business track featured speakers from three commercial users of FreeBSD: Cybernet, USWest, and Applix. Applix presented its port of Applixware Office for FreeBSD and explained how Applix has taken the core services of Applixware into open source. Commercial applications and open source were once a rare combination; we can only hope the trend away from that state of affairs will continue. Commercial use of FreeBSD The use of FreeBSD in embedded applications is increasing as well – and it is increasing at the same rate that hardware power is. These days, even inexpensive systems are able to run a BSD kernel. The BSD license and the solid TCP/IP stack prove significant enticements to this market as well. (Unlike the GNU Public License, the BSD license does not require that vendors make derivative works open source.) Companies such as USWest and Verio use FreeBSD for a wide variety of different Internet services. Yahoo! and Hotmail are examples of companies that use FreeBSD extensively for more specific purposes. Yahoo!, for example, has many hundreds of FreeBSD boxes, and Hotmail has almost 2000 FreeBSD machines at its data center in the San Francisco Bay area. Hotmail is owned by Microsoft, so the fact that it runs FreeBSD is a secret. Don’t tell anyone… When asked to comment on the increasing commercial interest in BSD, Hubbard said that FreeBSD is learning the Red Hat lesson. “Walnut Creek and others with business interests in FreeBSD have learned a few things from the Red Hat IPO,” he said, “and nobody is just sitting around now, content with business as usual. It’s clearly business as unusual in the open source world today.” Hubbard had also singled out some of BSD’s commercial partners, such as Whistle Communications, for praise in his opening day keynote. These partners play a key role in moving the project forward, he said, by contributing various enhancements and major new systems, such as Netgraph, as well as by contributing paid employee time spent on FreeBSD. Even short FreeBSD-related contacts can yield good results, Hubbard said. An example of this is the new jail() security code introduced in FreeBSD 3.x and 4.0, which was contributed by R & D Associates. A number of ISPs are also now donating the hardware and bandwidth that allows the project to provide more resource mirrors and experimental development sites. See you next year And speaking of corporate sponsors, thanks go to Walnut Creek for sponsoring the conference, and to Yahoo! for covering all the expenses involved in bringing the entire FreeBSD core team to Berkeley. As a fan of FreeBSD, I’m happy to see that the project has finally produced a conference. It was time: many of the 16 core team members had been working together on a regular basis for nearly seven years without actually meeting face to face. It’s been an interesting year for open source projects. I’m looking forward to the next year – and the next BSD conference – to be even better. ##News Roundup OpenBSD Recommends: Disable SMT/Hyperthreading in all Intel BIOSes Two recently disclosed hardware bugs affected Intel cpus: - TLBleed - T1TF (the name "Foreshadow" refers to 1 of 3 aspects of this bug, more aspects are surely on the way) Solving these bugs requires new cpu microcode, a coding workaround, *AND* the disabling of SMT / Hyperthreading. SMT is fundamentally broken because it shares resources between the two cpu instances and those shared resources lack security differentiators. Some of these side channel attacks aren't trivial, but we can expect most of them to eventually work and leak kernel or cross-VM memory in common usage circumstances, even such as javascript directly in a browser. There will be more hardware bugs and artifacts disclosed. Due to the way SMT interacts with speculative execution on Intel cpus, I expect SMT to exacerbate most of the future problems. A few months back, I urged people to disable hyperthreading on all Intel cpus. I need to repeat that: DISABLE HYPERTHREADING ON ALL YOUR INTEL MACHINES IN THE BIOS. Also, update your BIOS firmware, if you can. OpenBSD -current (and therefore 6.4) will not use hyperthreading if it is enabled, and will update the cpu microcode if possible. But what about 6.2 and 6.3? The situation is very complex, continually evolving, and is taking too much manpower away from other tasks. Furthermore, Intel isn't telling us what is coming next, and are doing a terrible job by not publically documenting what operating systems must do to resolve the problems. We are having to do research by reading other operating systems. There is no time left to backport the changes -- we will not be issuing a complete set of errata and syspatches against 6.2 and 6.3 because it is turning into a distraction. Rather than working on every required patch for 6.2/6.3, we will re-focus manpower and make sure 6.4 contains the best solutions possible. So please try take responsibility for your own machines: Disable SMT in the BIOS menu, and upgrade your BIOS if you can. I'm going to spend my money at a more trustworthy vendor in the future. ###Get Morrowind running on OpenBSD in 5 simple steps This article contains brief instructions on how to get one of the greatest Western RPGs of all time, The Elder Scrolls III: Morrowind, running on OpenBSD using the OpenMW open source engine recreation. These instructions were tested on a ThinkPad X1 Carbon Gen 3. The information was adapted from this OpenMW forum thread: https://forum.openmw.org/viewtopic.php?t=3510 Purchase and download the DRM-free version from GOG (also considered the best version due to the high quality PDF guide that it comes with): https://www.gog.com/game/theelderscrollsiiimorrowindgotyedition Install the required packages built from the ports tree as root. openmw is the recreated game engine, and innoextract is how we will get the game data files out of the win32 executable. pkgadd openmw innoextract Move the file from GOG setuptesmorrowindgoty2.0.0.7.exe into its own directory morrowind/ due to innoextract’s default behaviour of extracting into the current directory. Then type: innoextract setuptesmorrowindgoty2.0.0.7.exe Type openmw-wizard and follow the straightforward instructions. Note that you have a pre-existing installation, and select the morrowind/app/Data Files folder that innoextract extracted. Type in openmw-launcher, toggle the settings to your preferences, and then hit play! iXsystems https://twitter.com/allanjude/status/1034647571124367360 ###My First Clang Bug Part of the role of being a packager is compiling lots (and lots) of packages. That means compiling lots of code from interesting places and in a variety of styles. In my opinion, being a good packager also means providing feedback to upstream when things are bad. That means filing upstream bugs when possible, and upstreaming patches. One of the “exciting” moments in packaging is when tools change. So each and every major CMake update is an exercise in recompiling 2400 or more packages and adjusting bits and pieces. When a software project was last released in 2013, adjusting it to modern tools can become quite a chore (e.g. Squid Report Generator). CMake is excellent for maintaining backwards compatibility, generally accommodating old software with new policies. The most recent 3.12 release candidate had three issues filed from the FreeBSD side, all from fallout with older software. I consider the hours put into good bug reports, part of being a good citizen of the Free Software world. My most interesting bug this week, though, came from one line of code somewhere in Kleopatra: QUNUSED(gpgagentdata); That one line triggered a really peculiar link error in KDE’s FreeBSD CI system. Yup … telling the compiler something is unused made it fall over. Commenting out that line got rid of the link error, but introduced a warning about an unused function. Working with KDE-PIM’s Volker Krause, we whittled the problem down to a six-line example program — two lines if you don’t care much for coding style. I’m glad, at that point, that I could throw it over the hedge to the LLVM team with some explanatory text. Watching the process on their side reminds me ever-so-strongly of how things work in KDE (or FreeBSD for that matter): Bugzilla, Phabricator, and git combine to be an effective workflow for developers (perhaps less so for end-users). Today I got a note saying that the issue had been resolved. So brief a time for a bug. Live fast. Get squashed young. ###DragonFlyBSD Now Runs On The Threadripper 2990WX, Developer Shocked At Performance Last week I carried out some tests of BSD vs. Linux on the new 32-core / 64-thread Threadripper 2990WX. I tested FreeBSD 11, FreeBSD 12, and TrueOS – those benchmarks will be published in the next few days. I tried DragonFlyBSD, but at the time it wouldn’t boot with this AMD HEDT processor. But now the latest DragonFlyBSD development kernel can handle the 2990WX and the lead DragonFly developer calls this new processor “a real beast” and is stunned by its performance potential. When I tried last week, the DragonFlyBSD 5.2.2 stable release nor DragonFlyBSD 5.3 daily snapshot would boot on the 2990WX. But it turns out Matthew Dillon, the lead developer of DragonFlyBSD, picked up a rig and has it running now. So in time for the next 5.4 stable release or those using the daily snapshots can have this 32-core / 64-thread Zen+ CPU running on this operating system long ago forked from FreeBSD. In announcing his success in bringing up the 2990WX under DragonFlyBSD, which required a few minor changes, he shared his performance thoughts and hopes for the rig. “The cpu is a real beast, packing 32 cores and 64 threads. It blows away our dual-core Xeon to the tune of being +50% faster in concurrent compile tests, and it also blows away our older 4-socket Opteron (which we call ‘Monster’) by about the same margin. It’s an impressive CPU. For now the new beast is going to be used to help us improve I/O performance through the filesystem, further SMP work (but DFly scales pretty well to 64 threads already), and perhaps some driver to work to support the 10gbe on the mobo.” Dillon shared some results on the system as well. " The Threadripper 2990WX is a beast. It is at least 50% faster than both the quad socket opteron and the dual socket Xeon system I tested against. The primary limitation for the 2990WX is likely its 4 channels of DDR4 memory, and like all Zen and Zen+ CPUs, memory performance matters more than CPU frequency (and costs almost no power to pump up the performance). That said, it still blow away a dual-socket Xeon with 3x the number of memory channels. That is impressive!" The well known BSD developer also added, “This puts the 2990WX at par efficiency vs a dual-socket Xeon system, and better than the dual-socket Xeon with slower memory and a power cap. This is VERY impressive. I should note that the 2990WX is more specialized with its asymetric NUMA architecture and 32 cores. I think the sweet spot in terms of CPU pricing and efficiency is likely going to be with the 2950X (16-cores/32-threads). It is clear that the 2990WX (32-cores/64-threads) will max out 4-channel memory bandwidth for many workloads, making it a more specialized part. But still awesome…This thing is an incredible beast, I’m glad I got it.” While I have the FreeBSD vs. Linux benchmarks from a few days ago, it looks like now on my ever growing TODO list will be re-trying out the newest DragonFlyBSD daily snapshot for seeing how the performance compares in the mix. Stay tuned for the numbers that should be in the next day or two. ##Beastie Bits X11 on really small devices mandoc-1.14.4 released The pfSense Book is now available to everyone MWL: Burn it down! Burn it all down! Configuring OpenBSD: System and user config files for a more pleasant laptop FreeBSD Security Advisory: Resource exhaustion in TCP reassembly OpenBSD Foundation gets first 2018 Iridium donation New ZFS commit solves issue a few users reported in the feedback segment Project Trident should have a beta release by the end of next week Reminder about Stockholm BUG: September 5, 17:30-22:00 BSD-PL User Group: September 13, 18:30-21:00 Tarsnap ##Feedback/Questions Malcom - Having different routes per interface Bostjan - ZFS and integrity of data Michael - Suggestion for Monitoring Barry - Feedback Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

This is a live recording from a panel I moderated at the World Economic Forum Industry Strategy Meeting. The speakers included Shwetha Shetty Senior Director, Corporate Strategy Group, of SAP, Adam Ludwin, CEO of Chain, Brian Behlendorf, executive director of HyperLedger the Linux Foundation and Sheila Warren, project head of blockchain and distributed ledger technology at the World Economic Forum.We dive into the pros and cons of using blockchains for elections. which types of problems are best-suited to be solved by blockchain, why B2B applications of blockchain might come before B2C products and what kinds of identity-related data might be safe to put on a blockchain. Plus, Adam reveals some entertaining anecdotes about Silicon Valley safaris and how old World's Fair tickets could have an analog to blockchain systems today. Episodes I referenced during the discussion in case listeners want to dive more into the elections topic: Tomicah Tillemann episode on the blockchain voting pilot in West Virginia: http://unconfirmed.libsyn.com/battling-corruption-with-blockchain-technology-tomicah-tillemann-of-the-blockchain-trust-accelerator-ep018 Alex Gladstein episode with more on blockchain-based voting: http://unconfirmed.libsyn.com/alex-gladstein-of-the-human-rights-foundation-on-the-first-crypto-war-ep021 Tweets about blockchain-based voting: Matt Blaze's objecton to blockchain-based voting: https://twitter.com/mattblaze/status/1002921011854143488 Vitalik's response: https://twitter.com/VitalikButerin/status/1004203105611726849 Tomicah Tillemann's response: https://twitter.com/TomicahTD/status/1004325810252197888 To address the question at the end about blockchain-based passports:  2 Katie Haun episodes on using blockchain-based systems to solve the problems of "breeder documents" and fraud, waste and abuse: Fraud, waste and abuse: http://unchainedpodcast.co/live-from-inforum-at-the-commonwealth-club-blockchain-and-cryptocurrency-the-basics-with-kathryn-haun Breeder documents: http://unchainedpodcast.co/federal-prosecutor-kathryn-haun-on-how-criminals-use-bitcoin-and-how-she-catches-them  Episode with Vinny Lighal, founder of Civic, which is working on a blockchain-based identity solution: http://unchainedpodcast.co/bitcoin-oracle-vinny-lingham-on-why-bitcoin-is-overpriced  Thank you to our sponsor! Blockchain Warehouse: https://www.blockchainwarehouse.com

This is a live recording from a panel I moderated at the World Economic Forum Industry Strategy Meeting. The speakers included Shwetha Shetty Senior Director, Corporate Strategy Group, of SAP, Adam Ludwin, CEO of Chain, Brian Behlendorf, executive director of HyperLedger the Linux Foundation and Sheila Warren, project head of blockchain and distributed ledger technology at the World Economic Forum.We dive into the pros and cons of using blockchains for elections. which types of problems are best-suited to be solved by blockchain, why B2B applications of blockchain might come before B2C products and what kinds of identity-related data might be safe to put on a blockchain. Plus, Adam reveals some entertaining anecdotes about Silicon Valley safaris and how old World’s Fair tickets could have an analog to blockchain systems today. Episodes I referenced during the discussion in case listeners want to dive more into the elections topic: Tomicah Tillemann episode on the blockchain voting pilot in West Virginia: http://unconfirmed.libsyn.com/battling-corruption-with-blockchain-technology-tomicah-tillemann-of-the-blockchain-trust-accelerator-ep018 Alex Gladstein episode with more on blockchain-based voting: http://unconfirmed.libsyn.com/alex-gladstein-of-the-human-rights-foundation-on-the-first-crypto-war-ep021 Tweets about blockchain-based voting: Matt Blaze’s objecton to blockchain-based voting: https://twitter.com/mattblaze/status/1002921011854143488 Vitalik’s response: https://twitter.com/VitalikButerin/status/1004203105611726849 Tomicah Tillemann’s response: https://twitter.com/TomicahTD/status/1004325810252197888 To address the question at the end about blockchain-based passports:  2 Katie Haun episodes on using blockchain-based systems to solve the problems of "breeder documents" and fraud, waste and abuse: Fraud, waste and abuse: http://unchainedpodcast.co/live-from-inforum-at-the-commonwealth-club-blockchain-and-cryptocurrency-the-basics-with-kathryn-haun Breeder documents: http://unchainedpodcast.co/federal-prosecutor-kathryn-haun-on-how-criminals-use-bitcoin-and-how-she-catches-them  Episode with Vinny Lighal, founder of Civic, which is working on a blockchain-based identity solution: http://unchainedpodcast.co/bitcoin-oracle-vinny-lingham-on-why-bitcoin-is-overpriced  Thank you to our sponsor! Blockchain Warehouse: https://www.blockchainwarehouse.com

Chris speaks with the leads of two open source software foundations, Kris Borchers of the JavaScript Foundation, and Brian Behlendorf of the Hyperledge foundation at Collision conf. In the episode we speak about the progress of the foundations and open source software more broadly. http://gregariousmammal.com/podcast/ http://gregariousmammal.com/support http://facebook.com/gregariousmammal/ --- Send in a voice message: https://anchor.fm/theweeklysqueak/message

Interest in new blockchain technologies has exploded in the last year as the possibilities for applications keep rapidly expanding. One way to understand the blockchain revolution is through a technical discussion – something we did early in our What’s Now: San Francisco series with Brian Behlendorf. This month we looked at the financial side of...

The beauty of open-source software lies in its efficiency. If two companies, building different solutions, work together on the parts of the projects that overlap, they accomplish more in less time. The Hyperledger Project is an open-source collaboration working to build a set of blockchain technologies that can be used in a variety of industries and embedded in the emerging internet technology stack. Brian Behlendorf is the Executive Director of the Hyperledger Project for The Linux Foundation. Brian has dedicated his career to connecting and empowering the free and open-source software community to solve difficult problems. Early in his career, Brian was a primary developer of the Apache Web server and a founding member of the Apache Software Foundation. He was also the founding CTO of CollabNet and CTO of the World Economic Forum. Today, Brian serves on the board of the Mozilla Foundation as well as the Electronic Frontier Foundation. Prior to joining Hyperledger, Brian was a managing director at Mithril Capital Management, a global technology investment firm. Brian joins us to explain the relationship between the Linux Foundation and Hyperledger, describing the venture's subscription-based business model and several of the projects being built with its open-source blockchain technology. He walks us through the benefits of Hyperledger over public blockchains, discussing the business community's preference for anonymity and the right to fork if data is misused. Listen in for Brian's insight around measuring the progress of community-building and learn how open-source software helps us go further, faster. Connect with Brian Hyperledger https://www.hyperledger.org/ Hyperledger on YouTube https://www.youtube.com/channel/UC7_X0WkMtkWzaVUKF-PRBNQ Hyperledger on Facebook https://www.facebook.com/hyperledger Hyperledger on Twitter https://twitter.com/hyperledger Brian on Twitter https://twitter.com/brianbehlendorf Brian on LinkedIn https://www.linkedin.com/in/brianbehlendorf/ Brian's Website http://brian.behlendorf.com/ Resources Netcraft https://www.netcraft.com/ ‘Fighting the Seed Monopoly' in The Guardian https://www.theguardian.com/sustainable-business/seed-monopoly-free-seeds-farm-monsanto-dupont The Wind-Up Bird Chronicle by Haruki Murakami https://www.amazon.com/Wind-Up-Bird-Chronicle-Novel/dp/0679775439 Gödel, Escher, Bach: An Eternal Golden Braid by Douglas R. Hofstadter https://www.amazon.com/G%C3%B6del-Escher-Bach-Eternal-Golden/dp/0465026567 Connect with Boost VC Boost VC Website https://www.boost.vc/ Boost VC on Facebook https://www.facebook.com/boostvc/ Boost VC on Twitter https://twitter.com/BoostVC

On this episode of Web 3.0, we hear from Brian Behlendorf, the head of the Hyperledger project at the Linux Foundation, and leading figure in the open-source software movement. Brian began developing open-source code during the mid-1990's and was also the lead developer of Apache Web Server — one of the worlds most used pieces of software. Today, in the midst of a blockchain boom, Brian’s focus is still on free software development. I spoke with Brian in October. We were both in Cancun for Def Con 3. thirdweb.net https://www.hyperledger.org/

Interest in new blockchain technologies has exploded in the last year as the possibilities for applications keep rapidly expanding. One way to understand the blockchain revolution is through a technical discussion - something we did early in our What’s Now: San Francisco series with Brian Behlendorf. This month we will look at the financial side of blockchain - how those with money are wading into the space and how the revolution can get funded better and really scale up.

We explore decentralization, disruption and blockchain with a rockstar of the open-source software movement, Brian Behlendorf. The Executive Director of Hyperledger is attempting to build this next layer of the internet and believes there is a huge opportunity to put trust back into our broken systems.

Amber Baldet, JPMorgan Chase blockchain program lead, talks about what she was discussing at SXSW with Hyperledger executive director Brian Behlendorf and what themes she heard at the Ethereum Community Conference in Paris. She talks about privacy in financial transactions, how "immutable" blockchains might conflict with a new EU privacy law granting people the "right to be forgotten." And we briefly touch on her work with Jalak Jobanputra's new diversity-focused group Collective Future.  Privacy on Ethereum: https://www.coindesk.com/progress-hot-ethereum-privacy-projects-cooling-off/ The Collective Future: https://www.wired.com/story/for-women-in-cryptocurrency-a-new-effort-to-grow-their-ranks/ https://iapp.org/news/a/blockchain-technology-is-on-a-collision-course-with-eu-privacy-law/ Thank you to our sponsors: Preciate https://preciate.org/ which is seeking suggestions for who to appreciate at https://preciate.org/recognize/ and Quantstamp: https://quantstamp.com/ 

Amber Baldet, JPMorgan Chase blockchain program lead, talks about what she was discussing at SXSW with Hyperledger executive director Brian Behlendorf and what themes she heard at the Ethereum Community Conference in Paris. She talks about privacy in financial transactions, how "immutable" blockchains might conflict with a new EU privacy law granting people the "right to be forgotten." And we briefly touch on her work with Jalak Jobanputra's new diversity-focused group Collective Future.  Privacy on Ethereum: https://www.coindesk.com/progress-hot-ethereum-privacy-projects-cooling-off/ The Collective Future: https://www.wired.com/story/for-women-in-cryptocurrency-a-new-effort-to-grow-their-ranks/ https://iapp.org/news/a/blockchain-technology-is-on-a-collision-course-with-eu-privacy-law/ Thank you to our sponsors: Preciate https://preciate.org/ which is seeking suggestions for who to appreciate at https://preciate.org/recognize/ and Quantstamp: https://quantstamp.com/ 

Amber Baldet, JPMorgan Chase blockchain program lead, talks about what she was discussing at SXSW with Hyperledger executive director Brian Behlendorf and what themes she heard at the Ethereum Community Conference in Paris. She talks about privacy in financial transactions, how "immutable" blockchains might conflict with a new EU privacy law granting people the "right to be forgotten." And we briefly touch on her work with Jalak Jobanputra's new diversity-focused group Collective Future.  Privacy on Ethereum: https://www.coindesk.com/progress-hot-ethereum-privacy-projects-cooling-off/ The Collective Future: https://www.wired.com/story/for-women-in-cryptocurrency-a-new-effort-to-grow-their-ranks/ https://iapp.org/news/a/blockchain-technology-is-on-a-collision-course-with-eu-privacy-law/ Thank you to our sponsors: Preciate https://preciate.org/ which is seeking suggestions for who to appreciate at https://preciate.org/recognize/ and Quantstamp: https://quantstamp.com/ 

How the term open source was created, running FreeBSD on ThinkPad T530, Moving away from Windows, Unknown Giants, as well as OpenBSD and FreeDOS. This episode was brought to you by Headlines How I coined the term 'open source' (https://opensource.com/article/18/2/coining-term-open-source-software) In a few days, on February 3, the 20th anniversary of the introduction of the term "open source software" is upon us. As open source software grows in popularity and powers some of the most robust and important innovations of our time, we reflect on its rise to prominence. I am the originator of the term "open source software" and came up with it while executive director at Foresight Institute. Not a software developer like the rest, I thank Linux programmer Todd Anderson for supporting the term and proposing it to the group. This is my account of how I came up with it, how it was proposed, and the subsequent reactions. Of course, there are a number of accounts of the coining of the term, for example by Eric Raymond and Richard Stallman, yet this is mine, written on January 2, 2006. It has never been published, until today. The introduction of the term "open source software" was a deliberate effort to make this field of endeavor more understandable to newcomers and to business, which was viewed as necessary to its spread to a broader community of users. The problem with the main earlier label, "free software," was not its political connotations, but that—to newcomers—its seeming focus on price is distracting. A term was needed that focuses on the key issue of source code and that does not immediately confuse those new to the concept. The first term that came along at the right time and fulfilled these requirements was rapidly adopted: open source. This term had long been used in an "intelligence" (i.e., spying) context, but to my knowledge, use of the term with respect to software prior to 1998 has not been confirmed. The account below describes how the term open source software caught on and became the name of both an industry and a movement. Meetings on computer security In late 1997, weekly meetings were being held at Foresight Institute to discuss computer security. Foresight is a nonprofit think tank focused on nanotechnology and artificial intelligence, and software security is regarded as central to the reliability and security of both. We had identified free software as a promising approach to improving software security and reliability and were looking for ways to promote it. Interest in free software was starting to grow outside the programming community, and it was increasingly clear that an opportunity was coming to change the world. However, just how to do this was unclear, and we were groping for strategies. At these meetings, we discussed the need for a new term due to the confusion factor. The argument was as follows: those new to the term "free software" assume it is referring to the price. Oldtimers must then launch into an explanation, usually given as follows: "We mean free as in freedom, not free as in beer." At this point, a discussion on software has turned into one about the price of an alcoholic beverage. The problem was not that explaining the meaning is impossible—the problem was that the name for an important idea should not be so confusing to newcomers. A clearer term was needed. No political issues were raised regarding the free software term; the issue was its lack of clarity to those new to the concept. Releasing Netscape On February 2, 1998, Eric Raymond arrived on a visit to work with Netscape on the plan to release the browser code under a free-software-style license. We held a meeting that night at Foresight's office in Los Altos to strategize and refine our message. In addition to Eric and me, active participants included Brian Behlendorf, Michael Tiemann, Todd Anderson, Mark S. Miller, and Ka-Ping Yee. But at that meeting, the field was still described as free software or, by Brian, "source code available" software. While in town, Eric used Foresight as a base of operations. At one point during his visit, he was called to the phone to talk with a couple of Netscape legal and/or marketing staff. When he was finished, I asked to be put on the phone with them—one man and one woman, perhaps Mitchell Baker—so I could bring up the need for a new term. They agreed in principle immediately, but no specific term was agreed upon. Between meetings that week, I was still focused on the need for a better name and came up with the term "open source software." While not ideal, it struck me as good enough. I ran it by at least four others: Eric Drexler, Mark Miller, and Todd Anderson liked it, while a friend in marketing and public relations felt the term "open" had been overused and abused and believed we could do better. He was right in theory; however, I didn't have a better idea, so I thought I would try to go ahead and introduce it. In hindsight, I should have simply proposed it to Eric Raymond, but I didn't know him well at the time, so I took an indirect strategy instead. Todd had agreed strongly about the need for a new term and offered to assist in getting the term introduced. This was helpful because, as a non-programmer, my influence within the free software community was weak. My work in nanotechnology education at Foresight was a plus, but not enough for me to be taken very seriously on free software questions. As a Linux programmer, Todd would be listened to more closely. The key meeting Later that week, on February 5, 1998, a group was assembled at VA Research to brainstorm on strategy. Attending—in addition to Eric Raymond, Todd, and me—were Larry Augustin, Sam Ockman, and attending by phone, Jon "maddog" Hall. The primary topic was promotion strategy, especially which companies to approach. I said little, but was looking for an opportunity to introduce the proposed term. I felt that it wouldn't work for me to just blurt out, "All you technical people should start using my new term." Most of those attending didn't know me, and for all I knew, they might not even agree that a new term was greatly needed, or even somewhat desirable. Fortunately, Todd was on the ball. Instead of making an assertion that the community should use this specific new term, he did something less directive—a smart thing to do with this community of strong-willed individuals. He simply used the term in a sentence on another topic—just dropped it into the conversation to see what happened. I went on alert, hoping for a response, but there was none at first. The discussion continued on the original topic. It seemed only he and I had noticed the usage. Not so—memetic evolution was in action. A few minutes later, one of the others used the term, evidently without noticing, still discussing a topic other than terminology. Todd and I looked at each other out of the corners of our eyes to check: yes, we had both noticed what happened. I was excited—it might work! But I kept quiet: I still had low status in this group. Probably some were wondering why Eric had invited me at all. Toward the end of the meeting, the question of terminology was brought up explicitly, probably by Todd or Eric. Maddog mentioned "freely distributable" as an earlier term, and "cooperatively developed" as a newer term. Eric listed "free software," "open source," and "sourceware" as the main options. Todd advocated the "open source" model, and Eric endorsed this. I didn't say much, letting Todd and Eric pull the (loose, informal) consensus together around the open source name. It was clear that to most of those at the meeting, the name change was not the most important thing discussed there; a relatively minor issue. Only about 10% of my notes from this meeting are on the terminology question. But I was elated. These were some key leaders in the community, and they liked the new name, or at least didn't object. This was a very good sign. There was probably not much more I could do to help; Eric Raymond was far better positioned to spread the new meme, and he did. Bruce Perens signed on to the effort immediately, helping set up Opensource.org and playing a key role in spreading the new term. For the name to succeed, it was necessary, or at least highly desirable, that Tim O'Reilly agree and actively use it in his many projects on behalf of the community. Also helpful would be use of the term in the upcoming official release of the Netscape Navigator code. By late February, both O'Reilly & Associates and Netscape had started to use the term. Getting the name out After this, there was a period during which the term was promoted by Eric Raymond to the media, by Tim O'Reilly to business, and by both to the programming community. It seemed to spread very quickly. On April 7, 1998, Tim O'Reilly held a meeting of key leaders in the field. Announced in advance as the first "Freeware Summit," by April 14 it was referred to as the first "Open Source Summit." These months were extremely exciting for open source. Every week, it seemed, a new company announced plans to participate. Reading Slashdot became a necessity, even for those like me who were only peripherally involved. I strongly believe that the new term was helpful in enabling this rapid spread into business, which then enabled wider use by the public. A quick Google search indicates that "open source" appears more often than "free software," but there still is substantial use of the free software term, which remains useful and should be included when communicating with audiences who prefer it. A happy twinge When an early account of the terminology change written by Eric Raymond was posted on the Open Source Initiative website, I was listed as being at the VA brainstorming meeting, but not as the originator of the term. This was my own fault; I had neglected to tell Eric the details. My impulse was to let it pass and stay in the background, but Todd felt otherwise. He suggested to me that one day I would be glad to be known as the person who coined the name "open source software." He explained the situation to Eric, who promptly updated his site. Coming up with a phrase is a small contribution, but I admit to being grateful to those who remember to credit me with it. Every time I hear it, which is very often now, it gives me a little happy twinge. The big credit for persuading the community goes to Eric Raymond and Tim O'Reilly, who made it happen. Thanks to them for crediting me, and to Todd Anderson for his role throughout. The above is not a complete account of open source history; apologies to the many key players whose names do not appear. Those seeking a more complete account should refer to the links in this article and elsewhere on the net. FreeBSD on a Laptop - A guide to a fully functional installation of FreeBSD on a ThinkPad T530 (https://www.c0ffee.net/blog/freebsd-on-a-laptop) As I stated my previous post, I recently dug up my old ThinkPad T530 after the embarrassing stream of OS X security bugs this month. Although this ThinkPad ran Gentoo faithfully during my time in graduate school at Clemson, these days I'd much rather spend time my wife and baby than fighting with emerge and USE flags. FreeBSD has always been my OS of choice, and laptop support seems to be much better than it was a few years ago. In this guide, I'll show you the tweaks I made to wrestle FreeBSD into a decent experience on a laptop. Unlike my usual posts, this time I'm going to assume you're already pretty familiar with FreeBSD. If you're a layman looking for your first BSD-based desktop, I highly recommend checking out TrueOS (previously PC-BSD): they've basically taken FreeBSD and packaged it with all the latest drivers, along with a user-friendly installer and custom desktop environment out of the box. TrueOS is an awesome project–the only reason I don't use it is because I'm old, grumpy, and persnickety about having my operating system just so. Anyway, if you'd still like to take the plunge, read on. Keep in mind, I'm using a ThinkPad T530, but other ThinkPads of the same generation should be similarly compatible. Here's what you'll get: Decent battery life (8-9 hours with a new 9-cell battery) UEFI boot and full-disk encryption WiFi (Intel Ultimate-N 6300) Ethernet (Intel PRO/1000) Screen brightness adjustment Suspend/Resume on lid close (make sure to disable TPM in BIOS) Audio (Realtek ALC269 HDA, speakers and headphone jack) Keyboard multimedia buttons Touchpad/Trackpoint Graphics Acceleration (with integrated Intel graphics, NVIDIA card disabled in BIOS) What I haven't tested yet: Bluetooth Webcam Fingerprint reader SD Card slot Installation Power Saving Tweaks for Desktop Use X11 Fonts Login Manager: SLiM Desktop Environment: i3 Applications The LLVM Sanitizers stage accomplished (https://blog.netbsd.org/tnf/entry/the_llvm_sanitizers_stage_accomplished) I've managed to get the Memory Sanitizer to work for the elementary base system utilities, like ps(1), awk(1) and ksh(1). This means that the toolchain is ready for tests and improvements. I've iterated over the basesystem utilities and I looked for bugs, both in programs and in sanitizers. The number of detected bugs in the userland programs was low, there merely was one reading of an uninitialized variable in ps(1). A prebuilt LLVM toolchain I've prepared a prebuilt toolchain with Clang, LLVM, LLDB and compiler-rt for NetBSD/amd64. I prepared the toolchain on 8.99.12, however I have received reports that it works on other older releases. Link: llvm-clang-compilerrt-lldb-7.0.0beta_2018-01-24.tar.bz2 The archive has to be untarballed to /usr/local (however it might work to some extent in other paths). This toolchain contains a prebuilt tree of the LLVM projects from a snapshot of 7.0.0(svn). It is a pristine snapshot of HEAD with patches from pkgsrc-wip for llvm, clang, compiler-rt and lldb. Sanitizers Notable changes in sanitizers, all of them are in the context of NetBSD support. Added fstat(2) MSan interceptor. Support for kvm(3) interceptors in the common sanitizer code. Added devname(3) and devname_r(3) interceptors to the common sanitizer code. Added sysctl(3) familty of functions interceptors in the common sanitizer code. Added strlcpy(3)/strlcat(3) interceptors in the common sanitizer code. Added getgrouplist(3)/getgroupmembership(3) interceptors in the common sanitizer code. Correct ctype(3) interceptors in a code using Native Language Support. Correct tzset(3) interceptor in MSan. Correct localtime(3) interceptor in the common sanitizer code. Added paccept(2) interceptor to the common sanitizer code. Added access(2) and faccessat(2) interceptors to the common sanitizer code. Added acct(2) interceptor to the common sanitizer code. Added accept4(2) interceptor to the common sanitizer code. Added fgetln(3) interceptor to the common sanitizer code. Added interceptors for the pwcache(3)-style functions in the common sanitizer code. Added interceptors for the getprotoent(3)-style functions in the common sanitizer code. Added interceptors for the getnetent(3)-style functions in the common sanitizer code. Added interceptors for the fts(3)-style functions in the common sanitizer code. Added lstat(3) interceptor in MSan. Added strftime(3) interceptor in the common sanitizer code. Added strmode(3) interceptor in the common sanitizer code. Added interceptors for the regex(3)-style functions in the common sanitizer code. Disabled unwanted interceptor __sigsetjmp in TSan. Base system changes I've tidied up inclusion of the internal namespace.h header in libc. This has hidden the usage of public global symbol names of: strlcat -> _strlcat sysconf -> __sysconf closedir -> _closedir fparseln -> _fparseln kill -> _kill mkstemp -> _mkstemp reallocarr -> _reallocarr strcasecmp -> _strcasecmp strncasecmp -> _strncasecmp strptime -> _strptime strtok_r -> _strtok_r sysctl -> _sysctl dlopen -> __dlopen dlclose -> __dlclose dlsym -> __dlsym strlcpy -> _strlcpy fdopen -> _fdopen mmap -> _mmap strdup -> _strdup The purpose of these changes was to stop triggering interceptors recursively. Such interceptors lead to sanitization of internals of unprepared (not recompiled with sanitizers) prebuilt code. It's not trivial to sanitize libc's internals and the sanitizers are not designed to do so. This means that they are not a full replacement of Valgrind-like software, but a a supplement in the developer toolbox. Valgrind translates native code to a bytecode virtual machine, while sanitizers are designed to work with interceptors inside the pristine elementary libraries (libc, libm, librt, libpthread) and embed functionality into the executable's code. I've also reverted the vadvise(2) syscall removal, from the previous month. This caused a regression in legacy code recompiled against still supported compat layers. Newly compiled code will use a libc's stub of vadvise(2). I've also prepared a patch installing dedicated headers for sanitizers along with the base system GCC. It's still discussed and should land the sources soon. Future directions and goals Possible paths in random order: In the quartet of UBSan (Undefined Behavior Sanitizer), ASan (Address Sanitizer), TSan (Thread Sanitizer), MSan (Memory Sanitizer) we need to add the fifth basic sanitizer: LSan (Leak Sanitizer). The Leak Sanitizer (detector of memory leaks) demands a stable ptrace(2) interface for processes with multiple threads (unless we want to build a custom kernel interface). Integrate the sanitizers with the userland framework in order to ship with the native toolchain to users. Port sanitizers from LLVM to GCC. Allow to sanitize programs linked against userland libraries other than libc, librt, libm and libpthread; by a global option (like MKSANITIZER) producing a userland that is partially prebuilt with a desired sanitizer. This is required to run e.g. MSanitized programs against editline(3). So far, there is no Operating System distribution in existence with a native integration with sanitizers. There are 3rd party scripts for certain OSes to build a stack of software dependencies in order to validate a piece of software. Execute ATF tests with the userland rebuilt with supported flavors of sanitizers and catch regressions. Finish porting of modern linkers designed for large C++ software, such as GNU GOLD and LLVM LLD. Today the bottleneck with building the LLVM toolchain is a suboptimal linker GNU ld(1). I've decided to not open new battlefields and return now to porting LLDB and fixing ptrace(2). Plan for the next milestone Keep upstreaming a pile of local compiler-rt patches. Restore the LLDB support for traced programs with a single thread. Interview - Goran Mekic - meka@tilda.center (mailto:meka@tilda.center) / @meka_floss (https://twitter.com/meka_floss) CBSD website (https://bsdstore.ru) Jail and VM Manager *** News Roundup Finally Moving Away From Windows (https://www.manios.ca/blog/2018/01/finally-moving-away-from-windows/) Broken Window Thanks to a combination of some really impressive malware, bad clicking, and poor website choices, I had to blow away my Windows 10 installation. Not that it was Window's fault, but a piece of malware had infected my computer when I tried to download a long lost driver for an even longer lost RAID card for a server. A word of advice – the download you're looking for is never on an ad-infested forum in another language. In any case, I had been meaning to switch away from Windows soon. I didn't have my entire plan ready, but now was as good a time as any. My line of work requires me to maintain some form of Windows installation, so I decided to keep it in a VM rather than dual booting as I was developing code and not running any high-end visual stuff like games. My first thought was to install Arch or Gentoo Linux, but the last time I attempted a Gentoo installation it left me bootless. Not that there is anything wrong with Gentoo, it was probably my fault, but I like the idea of some sort of installer so I looked at rock-solid Debian. My dad had installed Debian on his sweet new cutting-edge Lenovo laptop he received recently from work. He often raves about his cool scripts and much more effective customized experience, but often complains about his hybrid GPU support as he has an Intel/Nvidia hybrid display adapter (he has finally resolved it and now boasts his 6 connected displays). I didn't want to install Windows again, but something didn't feel right about installing some flavour of Linux. Back at home I have a small collection of FreeBSD servers running in all sorts of jails and other physical hardware, with the exception of one Debian server which I had the hardest time dealing with (it would be FreeBSD too if 802.11ac support was there as it is acting as my WiFi/gateway/IDS/IPS). I loved my FreeBSD servers, and yes I will write posts about each one soon enough. I wanted that cleanliness and familiarity on my desktop as well (I really love the ports collection!). It's settled – I will run FreeBSD on my laptop. This also created a new rivalry with my father, which is not a bad thing either. Playing Devil's Advocate The first thing I needed to do was backup my Windows data. This was easy enough, just run a Windows Image Backup and it will- wait, what? Why isn't this working? I didn't want to fiddle with this too long because I didn't actually need an image just the data. I ended up just copying over the files to an external hard disk. Once that was done, I downloaded and verified the latest FreeBSD 11.1 RELEASE memstick image and flashed it to my trusty 8GB Verbatim USB stick. I've had this thing since 2007, it works great for being my re-writable “CD”. I booted it up and started the installation. I knew this installer pretty well as I had test-installed FreeBSD and OpenBSD in VMs when I was researching a Unix style replacement OS last year. In any case, I left most of the defaults (I didn't want to play with custom kernels right now) and I selected all packages. This downloaded them from the FreeBSD FTP server as I only had the memstick image. The installer finished and I was off to my first boot. Great! so far so good. FreeBSD loaded up and I did a ‘pkg upgrade' just to make sure that everything was up to date. Alright, time to get down to business. I needed nano. I just can't use vi, or just not yet. I don't care about being a vi-wizard, that's just too much effort for me. Anyway, just a ‘pkg install nano' and I had my editor. Next was obvious, I needed x11. XFCE was common, and there were plenty of tutorials out there. I wont bore you with those details, but it went something like ‘pkg install xfce' and I got all the dependencies. Don't forget to install SLiM to make it seamless. There are some configs in the .login I think. SLiM needs to be called once the boot drops you to the login so that you get SLiM's nice GUI login instead of the CLI login screen. Then SLiM passes you off to XFCE. I think I followed this and this. Awesome. Now that x11 is working, it's time to get all of my apps from Windows. Obviously, I can't get everything (ie. Visual Studio, Office). But in my Windows installation, I had chosen many open-source or cross-compiled apps as they either worked better or so that I was ready to move away from Windows at a moments notice. ‘pkg install firefox thunderbird hexchat pidgin gpa keepass owncloud-client transmission-qt5 veracrypt openvpn' were some immediate picks. There are a lot more that I downloaded later, but these are a few I use everyday. My laptop also has the same hybrid display adapter config that my dad's has, but I chose to only run Intel graphics, so dual screens are no problem for me. I'll add Nvidia support later, but it's not a priority. After I had imported my private keys and loaded my firefox and thunderbird settings, I wanted to get my Windows VM running right away as I was burning productive days at work fiddling with this. I had only two virtualisation options; qemu/kvm and bhyve. qemu/kvm wasn't available in pkg, and looked real dirty to compile, from FreeBSD's point of view. My dad is using qemu/kvm with virt-manager to manage all of his Windows/Unix VMs alike. I wanted that experience, but I also wanted packages that could be updated and I didn't want to mess up a compile. bhyve was a better choice. It was built-in, it was more compatible with Windows (from what I read), and this is a great step-by-step article for Windows 10 on FreeBSD 11 bhyve! I had already tried to get virt-manager to work with bhyve with no luck. I don't think libvirt connects with bhyve completely, or maybe my config is wrong. But I didn't have time to fiddle with it. I managed it all through command lines and that has worked perfectly so far. Well sorta, there was an issue installing SQL Server, and only SQL Server, on my Windows VM. This was due to a missing ‘sectorsize=512' setting on the disk parameter on the bhyve command line. That was only found after A LOT of digging because the SQL Server install didn't log the error properly. I eventually found out that SQL Server only likes one sector size of disks for the install and my virtual disk geometry was incorrect. Apps Apps Apps I installed Windows 10 on my bhyve VM and I got that all setup with the apps I needed for work. Mostly Office, Visual Studio, and vSphere for managing our server farm. Plus all of the annoying 3rd party VPN software (I'm looking at you Dell and Cisco). Alright, with the Windows VM done, I can now work at work and finish FreeBSD mostly during the nights. I still needed my remote files (I setup an ownCloud instance on a FreeNAS jail at home) so I setup the client. Now, normally on Windows I would come to work and connect to my home network using OpenVPN (again, I have a OpenVPN FreeNAS jail at home) and the ownCloud desktop would be able to handle changing DNS destination IPs Not on FreeBSD (and Linux too?). I ended up just configuring the ownCloud client to just connect to the home LAN IP for the ownCloud server and always connecting the OpenVPN to sync things. It kinda sucks, but at least it works. I left that running at home overnight to get a full sync (~130GB cloud sync, another reason I use it over Google or Microsoft). Once that was done I moved onto the fstab as I had another 1TB SSD in my laptop with other files. I messed around with fstab and my NFS shares to my FreeNAS at home, but took them out as they made the boot time so long when I wasn't at home. I would only mount them when my OpenVPN connected or manually. I really wanted to install SpaceFM, but it's only available as a package on Debian and their non-package install script doesn't work on FreeBSD (packages are named differently). I tried doing it manually, but it was too much work. As my dad was the one who introduced me to it, he still uses it as a use-case for his Debian setup. Instead I kept to the original PCManFM and it works just fine. I also loaded up my Bitcoin and Litecoin wallets and pointed them to the blockchain that I has used on Windows after their sync, they loaded perfectly and my balances were there. I kinda wish there was the Bitcoin-ABC full node Bitcoin Cash wallet package on FreeBSD, but I'm sure it will come out later. The rest is essentially just tweaks and making the environment more comfortable for me, and with most programs installed as packages I feel a lot better with upgrades and audit checking (‘pkg audit -F' is really helpful!). I will always hate Python, actually, I will always hate any app that has it's own package manager. I do miss the GUI GitHub tool on Windows. It was a really good-looking way to view all of my repos. The last thing (which is increasing it's priority every time I go to a social media site or YouTube) is fonts. My god I never thought it was such a problem, and UTF support is complicated. If anyone knows how to get all UTF characters to show up, please let me know. I'd really like Wikipedia articles to load perfectly (I followed this post and there are still some missing). There are some extra tweaks I followed here and here. Conclusion I successfully migrated from Windows 10 to FreeBSD 11.1 with minimal consequence. Shout out goes to the entire FreeBSD community. So many helpful people in there, and the forums are a great place to find tons of information. Also thanks to the ones who wrote the how-to articles I've referenced. I never would have gotten bhyve to work and I'd still probably be messing with my X config without them. I guess my take home from this is to not be afraid to make changes that may change how comfortable I am in an environment. I'm always open to comments and questions, please feel free to make them below. I purposefully didn't include too many technical things or commands in this article as I wanted to focus on the larger picture of the migration as a whole not the struggles of xorg.conf, but if you would like to see some of the configs or commands I used, let me know and I'll include some! TrueOS Rules of Conduct (https://www.trueos.org/rulesofconduct/) We believe code is truly agnostic and embrace inclusiveness regardless of a person's individual beliefs. As such we only ask the following when participating in TrueOS public events and digital forums: Treat each other with respect and professionalism. Leave personal and TrueOS unrelated conversations to other channels. In other words, it's all about the code. Users who feel the above rules have been violated in some way can register a complaint with abuse@trueos.org + Shorter than the BSD License (https://twitter.com/trueos/status/965994363070353413) + Positive response from the community (https://twitter.com/freebsdbytes/status/966567686015782912) I really like the @TrueOS Code of Conduct, unlike some other CoCs. It's short, clear and covers everything. Most #OpenSource projects are labour of love. Why do you need a something that reads like a legal contract? FreeBSD: The Unknown Giant (https://neomoevius.tumblr.com/post/171108458234/freebsd-the-unknown-giant) I decided to write this article as a gratitude for the recent fast answer of the FreeBSD/TrueOS community with my questions and doubts. I am impressed how fast and how they tried to help me about this operating system which I used in the past(2000-2007) but recently in 2017 I began to use it again. + A lot has changed in 10 years I was looking around the internet, trying to do some research about recent information about FreeBSD and other versions or an easy to use spins like PCBSD (now TrueOS) I used to be Windows/Mac user for so many years until 2014 when I decided to use Linux as my desktop OS just because I wanted to use something different. I always wanted to use unix or a unix-like operating system, nowadays my main objective is to learn more about these operating systems (Debian Linux, TrueOS or FreeBSD). FreeBSD has similarities with Linux, with two major differences in scope and licensing: FreeBSD maintains a complete operating system, i.e. the project delivers kernel, device drivers, userland utilities and documentation, as opposed to Linux delivering a kernel and drivers only and relying on third-parties for system software; and FreeBSD source code is generally released under a permissive BSD license as opposed to the copyleft GPL used by Linux.“ But why do I call FreeBSD “The Unknown Giant”?, because the code base of this operating system has been used by other companies to develop their own operating system for products like computers or also game consoles. + FreeBSD is used for storage appliances, firewalls, email scanners, network scanners, network security appliances, load balancers, video servers, and more So many people now will learn that not only “linux is everywhere” but also that “FreeBSD is everywhere too” By the way speaking about movies, Do you remember the movie “The Matrix”? FreeBSD was used to make the movie: “The photo-realistic surroundings generated by this method were incorporated into the bullet time scene, and linear interpolation filled in any gaps of the still images to produce a fluent dynamic motion; the computer-generated “lead in” and “lead out” slides were filled in between frames in sequence to get an illusion of orbiting the scene. Manex Visual Effects used a cluster farm running the Unix-like operating system FreeBSD to render many of the film's visual effects” + FreeBSD Press Release re: The Matrix (https://www.freebsd.org/news/press-rel-1.html) I hope that I gave a good reference, information and now so many people can understand why I am going to use just Debian Linux and FreeBSD(TrueOS) to do so many different stuff (music, 3d animation, video editing and text editing) instead use a Mac or Windows. + FreeBSD really is the unknown giant. OpenBSD and FreeDOS vs the hell in earth (https://steemit.com/openbsd/@npna/openbsd-and-freedos-vs-the-hell-in-earth) Yes sir, yes. Our family, composed until now by OpenBSD, Alpine Linux and Docker is rapidly growing. And yes, sir. Yes. All together we're fighting against your best friends, the infamous, the ugliest, the worst...the dudes called the privacy cannibals. Do you know what i mean, sure? We're working hard, no matter what time is it, no matter in what part in the world we are, no matter if we've no money. We perfectly know that you cannot do nothing against the true. And we're doing our best to expand our true, our doors are opened to all the good guys, there's a lot here but their brain was fucked by your shit tv, your fake news, your laws, etc etc etc. We're alive, we're here to fight against you. Tonight, yes it's a Friday night and we're working, we're ready to welcome with open arms an old guy, his experience will give us more power. Welcome to: FreeDOS But why we want to build a bootable usb stick with FreeDOS under our strong OpenBSD? The answer is as usual to fight against the privacy cannibals! More than one decade ago the old BIOS was silently replaced by the more capable and advanced UEFI, this is absolutely normal because of the pass of the years and exponencial grow of the power of our personal computers. UEFI is a complex system, it's like a standalone system operative with direct access to every component of our (yes, it's our not your!) machine. But...wait a moment...do you know how to use it? Do you ever know that it exist? And one more thing, it's secure? The answer to this question is totally insane, no, it's not secure. The idea is good, the company that started in theory is one of the most important in IT, it's Intel. The history is very large and obviously we're going to go very deep in it, but trust me UEFI and the various friend of him, like ME, TPM are insecure and closed source! Like the hell in earth. A FreeDOS bootable usb image under OpenBSD But let's start preparing our OpenBSD to put order in this chaos: $ mkdir -p freedos/stuff $ cd freedos/stuff $ wget https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdboot.img $ wget https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/sys-freedos-linux.zip $ wget https://download.lenovo.com/consumer/desktop/o35jy19usa_y900.exe $ wget http://145.130.102.57/domoticx/software/amiflasher/AFUDOS%20Flasher%205.05.04.7z Explanation in clear language as usual: create two directory, download the minimal boot disc image of FreeDOS, download Syslinux assembler MBR bootloaders, download the last Windows only UEFI update from Lenovo and download the relative unknown utility from AMI to flash our motherboard UEFI chipset. Go ahead: $ doas pkg_add -U nasm unzip dosfstools cabextract p7zip nasm the Netwide Assembler, a portable 80x86 assembler. unzip list, test and extract compressed files in a ZIP archive. dosfstoolsa collections of utilities to manipulate MS-DOSfs. cabextract program to extract files from cabinet. p7zipcollection of utilities to manipulate 7zip archives. $ mkdir sys-freedos-linux && cd sys-freedos-linux $ unzip ../sys-freedos-linux.zip $ cd ~/freedos && mkdir old new $ dd if=/dev/null of=freedos.img bs=1024 seek=20480 $ mkfs.fat freedos.img Create another working directory, cd into it, unzip the archive that we've downloaded, return to the working root and create another twos directories. dd is one of the most important utilities in the unix world to manipulate at byte level input and output: The dd utility copies the standard input to the standard output, applying any specified conversions. Input data is read and written in 512-byte blocks. If input reads are short, input from multiple reads are aggregated to form the output block. When finished, dd displays the number of complete and partial input and output blocks and truncated input records to the standard error output. We're creating here a virtual disk with bs=1024 we're setting both input and output block to 1024bytes; with seek=20480 we require 20480bytes. This is the result: -rw-r--r-- 1 taglio taglio 20971520 Feb 3 00:11 freedos.img. Next we format the virtual disk using the MS-DOS filesystem. Go ahead: $ doas su $ perl stuff/sys-freedos-linux/sys-freedos.pl --disk=freedos.img $ vnconfig vnd0 stuff/fdboot.img $ vnconfig vnd1 freedos.img $ mount -t msdos /dev/vnd0c old/ $ mount -t msdos /dev/vnd1c new/ We use the perl utility from syslinux to write the MBR of our virtual disk freedos.img. Next we create to loop virtual node using the OpenBSD utility vnconfig. Take care here because it is quite different from Linux, but as usual is clear and simple. The virtual nodes are associated to the downloaded fdboot.img and the newly created freedos.img. Next we mount the two virtual nodes cpartitions; in OpenBSD cpartition describes the entire physical disk. Quite different from Linux, take care. $ cp -R old/* new/ $ cd stuff $ mkdir o35jy19usa $ cabextract -d o35jy19usa o35jy19usa_y900.exe $ doas su $ cp o35jy19usa/ ../new/ $ mkdir afudos && cd afudos $ 7z e ../AFUDOS* $ doas su $ cp AFUDOS.exe ../../new/ $ umount ~/freedos/old/ && umount ~/freedos/new/ $ vnconfig -u vnd1 && vnconfig -u vnd0 Copy all files and directories in the new virtual node partition, extract the Lenovo cabinet in a new directory, copy the result in our new image, extract the afudos utility and like the others copy it. Umount the partitions and destroy the loop vnode. Beastie Bits NetBSD - A modern operating system for your retro battlestation (https://www.geeklan.co.uk/files/fosdem2018-retro) FOSDEM OS distribution (https://twitter.com/pvaneynd/status/960181163578019840/photo/1) Update on two pledge-related changes (https://marc.info/?l=openbsd-tech&m=151268831628549) *execpromises (https://marc.info/?l=openbsd-cvs&m=151304116010721&w=2) Slides for (BSD from scratch - from source to OS with ease on NetBSD) (https://www.geeklan.co.uk/files/fosdem2018-bsd/) Goobyte LastPass: You're fired! (https://blog.crashed.org/goodbye-lastpass/) *** Feedback/Questions Scott - ZFS Mirror with SLOG (http://dpaste.com/22Z8C6Z#wrap) Troels - Question about compressed ARC (http://dpaste.com/3X2R1BV#wrap) Jeff - FreeBSD Desktop DNS (http://dpaste.com/2BQ9HFB#wrap) Jonathon - Bhyve and gpu passthrough (http://dpaste.com/0TTT0DB#wrap) ***

Many people have heard of bitcoin and might know something about blockchain, the technology system underlying the crypto currency. Yet few people understand how important blockchain technology could be not just for financial tech, but also for almost every other field. Blockchain develops transparent ledgers in distributed databases that can’t be tampered with, thus ensuring complete trust in transactions between strangers. In the near future, blockchain could track parts in a supply chain, or medical records, or votes in a ballot box.

We went back into the archives to conversations we had around blockchains and databases at OSCON 2017. We talked with Monty Widenius, creator of MariaDB the open source forever fork MySQL, Brian Behlendorf, Executive Director of Hyperledger, the open source collaborative effort hosted by The Linux Foundation to advance blockchain technologies, and Tague Griffith, Head of Developer Advocacy at Redis Labs, the home of open source Redis and commercial provider of Redis Enterprise.

We went back into the archives to conversations we had around blockchains and databases at OSCON 2017. We talked with Monty Widenius, creator of MariaDB the open source forever fork MySQL, Brian Behlendorf, Executive Director of Hyperledger, the open source collaborative effort hosted by The Linux Foundation to advance blockchain technologies, and Tague Griffith, Head of Developer Advocacy at Redis Labs, the home of open source Redis and commercial provider of Redis Enterprise.

This week Bitcoin has gone the the moon! So what's the story behind its new all time high price? And how might the long courtship between Wall Street and Bitcoin have played a part in the story? The guys take a look at the JP Morgan messaging on Bitcoin, including Jamie Dimon's views. We cover news from both Swell and Sibos, the pseudonymous nature of Bitcoin and how SWIFT intend to respond to the changing payments landscape. PLus, how is IBM using cryptocurrency in cross-border payments? Colin explains why open blockchains might be the canary in the coalmine and, while the People's Bank of China Digital Currency Director calls for a centralised state cryptocurrency, Simon asks whether it's really possible to have a true cryptocurrency that's centralised. Plus, what can all this mean for a possible CryptoRuble? We return to the story of the legal battle between R3 and Ripple to find out who's in the ascendancy, and the guys discuss how Digital Asset Holdings intend to use the $40m series B funding they raised recently. And of course, we also revisit Segwit2x for an update on its progress, and discuss Ethereum's own Byznatium fork. Plus, interviews with Brian Behlendorf, Executive Director of the Hyperledger Project (https://www.hyperledger.org/) within the Linux Foundation, and Paul Worrall, founder of Zonafide (https://www.zonafide.net/). We hope you enjoy the show - don't forget to subscribe so you never miss an episode! Want to join the conversation on all the topics discussed? Tweet the show @bchaininsider or read more about the news stories and add your own thoughts at fintechinsidernews.com (https://fintechinsidernews.com/). And if you really love the show, why not leave us a review on iTunes? Special Guests: Brian Behlendorf and Paul Worrall.

In this episode of AFP Conversations, host Ira Apfel talks with Brian Behlendorf, executive director of Hyperledger, an open-source community working to create blockchain technologies for business. Behlendorf has plenty of experience with two of the most popular open-source communities on the web, Apache Web and Mozilla Firefox. He’s also served on the board of the Mozilla Foundation and the Electronic Frontier Foundation. Thanks for listening to AFP Conversations. Please give it a review on your podcast app of choice -- it will help other listeners find the show, and host Ira Apfel will read your review on air. 

Brian Behlendorf is a legend in the open software movement. He is one of the creators of Apache – server software that powers most websites on the internet. He currently serves as Executive Director of Hyperledger – one of the most prominent Blockchain consortiums in the world. His list of accomplishments in the tech industry is beyond impressive:  Technology Advisor – White House & 2008 Obama Presidential Campaign President – Apache Software Foundation CTO – World Economic Forum Managing Director – Mithril Capital Management (venture capital firm) Board member – Mozilla Foundation, Benetech, Electronic Frontier Foundation  In this episode, Brian and I discuss the history of Hyperledger, the 8 projects under the Hyperledger banner (including several interesting use cases), and what Brian really thinks about the current ICO and cryptocurrency craze.

I speak with Brian Behlendorf, one of the key developers behind the Apache Web Server, a Mozilla and EFF board member, and Executive Director of the Hyperledger foundation, a project that aims to bring Blockchain mainstream. --- Send in a voice message: https://anchor.fm/theweeklysqueak/message

In this episode, we talk with Brian Behlendorf, the Executive Director of the Hyperledger Project at The Linux Foundation. We discuss the different ways that blockchain can revolutionize the industries that can benefit from it.

As a lead developer of the Apache webserver and founder of the Apache Software Foundation, Brian Behlendorf has played a central role in building internet architecture. Recently, he became Executive Director of the Hyperledger Project that aims to build foundational blockchain technology in an open-source, collaborative way. Topics covered in this episode: Brian’s role in the development of the Apache server and Apache Software Foundation The flaws in how blockchain software is currently being developed Why blockchain needs a foundation to steer the development of its foundational technology The key lessons from the Apache Software Foundation that inform Hyperledger’s approach Hyperledger’s membership and organizational structure The role of software licenses and why he favors Apache Episode links: Hyperledger Website Brian Behlendorf's Wikipedia page Brian Behlendorf's Website Blockchain Meetup Berlin Hyperledger Talk This episode is hosted by Brian Fabian Crain and Meher Roy. Show notes and listening options: epicenter.tv/160

This time on the show, we'll be talking with Justin Cormack about NetBSD rump kernels. We'll learn how to run them on other operating systems, what's planned for the future and a lot more. As always, answers to viewer-submitted questions and all the news for the week, on BSD Now - the place to B.. SD. This episode was brought to you by Headlines EuroBSDCon 2014 talks and tutorials (http://2014.eurobsdcon.org/talks-and-schedule/) The 2014 EuroBSDCon videos have been online for over a month, but unannounced - keep in mind these links may be temporary (but we'll mention their new location in a future show and fix the show notes if that's the case) Arun Thomas, BSD ARM Kernel Internals (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/01.BSD-ARM%20Kernel%20Internals%20-%20Arun%20Thomas.mp4) Ted Unangst, Developing Software in a Hostile Environment (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/02.Developing%20Software%20in%20a%20Hostile%20Environment%20-%20Ted%20Unangst.mp4) Martin Pieuchot, Taming OpenBSD Network Stack Dragons (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/03.Taming%20OpenBSD%20Network%20Stack%20Dragons%20-%20Martin%20Pieuchot.mp4) Henning Brauer, OpenBGPD turns 10 years (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/04.OpenBGPD%20turns%2010%20years%20-%20%20Henning%20Brauer.mp4) Claudio Jeker, vscsi and iscsid iSCSI initiator the OpenBSD way (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/05.vscsi(4)%20and%20iscsid%20-%20iSCSI%20initiator%20the%20OpenBSD%20way%20-%20Claudio%20Jeker.mp4) Paul Irofti, Making OpenBSD Useful on the Octeon Network Gear (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/03.Saturday/06.Making%20OpenBSD%20Useful%20on%20the%20Octeon%20Network%20Gear%20-%20Paul%20Irofti.mp4) Baptiste Daroussin, Cross Building the FreeBSD ports tree (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/01.Cross%20Building%20the%20FreeBSD%20ports%20tree%20-%20Baptiste%20Daroussin.mp4) Boris Astardzhiev, Smartcom's control plane software, a customized version of FreeBSD (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/02.Smartcom%e2%80%99s%20control%20plane%20software,%20a%20customized%20version%20of%20FreeBSD%20-%20Boris%20Astardzhiev.mp4) Michał Dubiel, OpenStack and OpenContrail for FreeBSD platform (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/03.OpenStack%20and%20OpenContrail%20for%20FreeBSD%20platform%20-%20Micha%c5%82%20Dubiel.mp4) Martin Husemann & Joerg Sonnenberger, Tool-chaining the Hydra, the ongoing quest for modern toolchains in NetBSD (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/04.(Tool-)chaining%20the%20Hydra%20The%20ongoing%20quest%20for%20modern%20toolchains%20in%20NetBSD%20-%20Martin%20Huseman%20&%20Joerg%20Sonnenberger.mp4) Taylor R Campbell, The entropic principle: /dev/u?random and NetBSD (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/05.The%20entropic%20principle:%20dev-u%3frandom%20and%20NetBSD%20-%20Taylor%20R%20Campbell.mp4) Dag-Erling Smørgrav, Securing sensitive & restricted data (https://va.ludost.net/files/eurobsdcon/2014/Rodopi/04.Sunday/06.Securing%20sensitive%20&%20restricted%20data%20-%20Dag-Erling%20Sm%c3%b8rgrav.mp4) Peter Hansteen, Building The Network You Need (https://va.ludost.net/files/eurobsdcon/2014/Pirin/01.Thursday/01.Building%20The%20Network%20You%20Need%20With%20PF%20-%20Peter%20Hansteen.mp4) With PF (https://va.ludost.net/files/eurobsdcon/2014/Pirin/01.Thursday/02.Building%20The%20Network%20You%20Need%20With%20PF%20-%20Peter%20Hansteen.mp4) Stefan Sperling, Subversion for FreeBSD developers (https://va.ludost.net/files/eurobsdcon/2014/Pirin/01.Thursday/03.Subversion%20for%20FreeBSD%20developers%20-%20Stefan%20Sperling.mp4) Peter Hansteen, Transition to (https://va.ludost.net/files/eurobsdcon/2014/Pirin/02.Friday/01.Transition%20to%20OpenBSD%205.6%20-%20Peter%20Hansteen.mp4) OpenBSD 5.6 (https://va.ludost.net/files/eurobsdcon/2014/Pirin/02.Friday/02.Transition%20to%20OpenBSD%205.6%20-%20Peter%20Hansteen.mp4) Ingo Schwarze, Let's make manuals (https://va.ludost.net/files/eurobsdcon/2014/Pirin/02.Friday/03.Let%e2%80%99s%20make%20manuals%20more%20useful%20-%20Ingo%20Schwarze.mp4) more useful (https://va.ludost.net/files/eurobsdcon/2014/Pirin/02.Friday/04.Let%e2%80%99s%20make%20manuals%20more%20useful%20-%20Ingo%20Schwarze.mp4) Francois Tigeot, Improving DragonFly's performance with PostgreSQL (https://va.ludost.net/files/eurobsdcon/2014/Pirin/03.Saturday/01.Improving%20DragonFly%e2%80%99s%20performance%20with%20PostgreSQL%20-%20Francois%20Tigeot.mp4) Justin Cormack, Running Applications on the NetBSD Rump Kernel (https://va.ludost.net/files/eurobsdcon/2014/Pirin/03.Saturday/02.Running%20Applications%20on%20the%20NetBSD%20Rump%20Kernel%20-%20Justin%20Cormack.mp4) Pierre Pronchery, EdgeBSD, a year later (https://va.ludost.net/files/eurobsdcon/2014/Pirin/03.Saturday/04.EdgeBSD,%20a%20year%20later%20-%20%20Pierre%20Pronchery.mp4) Peter Hessler, Using routing domains or tables in a production network (https://va.ludost.net/files/eurobsdcon/2014/Pirin/03.Saturday/05.Using%20routing%20domains%20or%20tables%20in%20a%20production%20network%20-%20%20Peter%20Hessler.mp4) Sean Bruno, QEMU user mode on FreeBSD (https://va.ludost.net/files/eurobsdcon/2014/Pirin/03.Saturday/06.QEMU%20user%20mode%20on%20FreeBSD%20-%20%20Sean%20Bruno.mp4) Kristaps Dzonsons, Bugs Ex Ante (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/01.Bugs%20Ex%20Ante%20-%20Kristaps%20Dzonsons.mp4) Yann Sionneau, Porting NetBSD to the LatticeMico32 open source CPU (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/02.Porting%20NetBSD%20to%20the%20LatticeMico32%20open%20source%20CPU%20-%20Yann%20Sionneau.mp4) Alexander Nasonov, JIT Code Generator for NetBSD (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/03.JIT%20Code%20Generator%20for%20NetBSD%20-%20Alexander%20Nasonov.mp4) Masao Uebayashi, Porting Valgrind to NetBSD and OpenBSD (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/04.Porting%20Valgrind%20to%20NetBSD%20and%20OpenBSD%20-%20Masao%20Uebayashi.mp4) Marc Espie, parallel make, working with legacy code (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/05.parallel%20make:%20working%20with%20legacy%20code%20-%20Marc%20Espie.mp4) Francois Tigeot, Porting the drm-kms graphic drivers to DragonFly (https://va.ludost.net/files/eurobsdcon/2014/Pirin/04.Sunday/06.Porting%20the%20drm-kms%20graphic%20drivers%20to%20DragonFly%20-%20Francois%20Tigeot.mp4) The following talks (from the Vitosha track room) are all currently missing: Jordan Hubbard, FreeBSD, Looking forward to another 10 years (but we have another recording) Theo de Raadt, Randomness, how arc4random has grown since 1998 (but we have another recording) Kris Moore, Snapshots, Replication, and Boot-Environments Kirk McKusick, An Introduction to the Implementation of ZFS John-Mark Gurney, Optimizing GELI Performance Emmanuel Dreyfus, FUSE and beyond, bridging filesystems Lourival Vieira Neto, NPF scripting with Lua Andy Tanenbaum, A Reimplementation of NetBSD Based on a Microkernel Stefano Garzarella, Software segmentation offloading for FreeBSD Ted Unangst, LibreSSL Shawn Webb, Introducing ASLR In FreeBSD Ed Maste, The LLDB Debugger in FreeBSD Philip Guenther, Secure lazy binding *** OpenBSD adopts SipHash (https://www.marc.info/?l=openbsd-tech&m=141614801713457&w=2) Even more DJB crypto somehow finds its way into OpenBSD's base system This time it's SipHash (https://131002.net/siphash/), a family of pseudorandom functions that's resistant to hash bucket flooding attacks while still providing good performance After an initial import (http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/crypto/siphash.c?rev=1.1&content-type=text/x-cvsweb-markup) and some clever early usage (https://www.marc.info/?l=openbsd-cvs&m=141604896822253&w=2), a few developers agreed that it would be better to use it in a lot more places It will now be used in the filesystem, and the plan is to utilize it to protect all kernel hash functions Some other places (http://www.bsdnow.tv/episodes/2013_12_18-cryptocrystalline) that Bernstein's work can be found in OpenBSD include the ChaCha20-Poly1305 authenticated stream cipher and Curve25519 KEX used in SSH, ChaCha20 used in the RNG, and Ed25519 keys used in signify (http://www.bsdnow.tv/episodes/2014_02_05-time_signatures) and SSH *** FreeBSD 10.1-RELEASE (https://www.freebsd.org/releases/10.1R/announce.html) FreeBSD's release engineering team (http://www.bsdnow.tv/episodes/2013-09-11_engineering_powder_kegs) likes to troll us by uploading new versions just a few hours after we finish recording an episode The first maintenance update for the 10.x branch is out, improving upon a lot of things found in 10.0-RELEASE The vt driver was merged from -CURRENT and can now be enabled with a loader.conf switch (and can even be used on a PlayStation 3) Bhyve has gotten quite a lot of fixes and improvements from its initial debut in 10.0, including boot support for ZFS Lots of new ARM hardware is supported now, including SMP support for most of them A new kernel selection menu was added to the loader, so you can switch between newer and older kernels at boot time 10.1 is the first to support UEFI booting on amd64, which also has serial console support now Lots of third party software (OpenSSH, OpenSSL, Unbound..) and drivers have gotten updates to newer versions It's a worthy update from 10.0, or a good time to try the 10.x branch if you were avoiding the first .0 release, so grab an ISO (http://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.1/) or upgrade (https://www.freebsd.org/cgi/man.cgi?query=freebsd-update) today Check the detailed release notes (https://www.freebsd.org/releases/10.1R/relnotes.html) for more information on all the changes Also take a look at some of the known problems (https://www.freebsd.org/releases/10.1R/errata.html#open-issues) to see if (https://forums.freebsd.org/threads/segmentation-fault-while-upgrading-from-10-0-release-to-10-1-release.48977/) you'll (https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080599.html) be (https://forums.freebsd.org/threads/10-0-10-1-diocaddrule-operation-not-supported-by-device.49016/) affected (https://www.reddit.com/r/freebsd/comments/2mmzzy/101release_restart_problems_anyone/) by any of them PC-BSD was also updated accordingly (http://wiki.pcbsd.org/index.php/What%27s_New/10.1) with some of their own unique features and changes *** arc4random - Randomization for All Occasions (https://www.youtube.com/watch?v=aWmLWx8ut20) Theo de Raadt gave an updated version of his EuroBSDCon presentation at Hackfest 2014 in Quebec The presentation is mainly about OpenBSD's arc4random function, and outlines the overall poor state of randomization in the 90s and how it has evolved in OpenBSD over time It begins with some interesting history on OpenBSD and how it became a security-focused OS - in 1996, their syslogd got broken into and "suddenly we became interested in security" The talk also touches on how low-level changes can shake up the software ecosystem and third party packages that everyone uses There's some funny history on the name of the function (being called arc4random despite not using RC4 anymore) and an overall status update on various platforms' usage of it Very detailed and informative presentation, and the slides can be found here (http://www.openbsd.org/papers/hackfest2014-arc4random/index.html) A great quote from the beginning: "We consider ourselves a community of (probably rather strange) people who work on software specifically for the purpose of trying to make it better. We take a 'whole-systems' approach: trying to change everything in the ecosystem that's under our control, trying to see if we can make it better. We gain a lot of strength by being able to throw backwards compatibility out the window. So that means that we're able to do research and the minute that we decide that something isn't right, we'll design an alternative for it and push it in. And if it ends up breaking everybody's machines from the previous stage to the next stage, that's fine because we'll end up in a happier place." *** Interview - Justin Cormack - justin@netbsd.org (mailto:justin@netbsd.org) / @justincormack (https://twitter.com/justincormack) NetBSD on Xen, rump kernels, various topics News Roundup The FreeBSD foundation's biggest donation (http://freebsdfoundation.blogspot.com/2014/11/freebsd-foundation-announces-generous.html) The FreeBSD foundation has a new blog post about the largest donation they've ever gotten From the CEO of WhatsApp comes a whopping one million dollars in a single donation It also has some comments from the donor about why they use BSD and why it's important to give back Be sure to donate to the foundation of whatever BSD you use when you can - every little bit helps, especially for OpenBSD (http://www.openbsd.org/donations.html), NetBSD (https://www.netbsd.org/donations/) and DragonFly (http://www.dragonflybsd.org/donations/) who don't have huge companies supporting them regularly like FreeBSD does *** OpenZFS Dev Summit 2014 videos (http://open-zfs.org/wiki/OpenZFS_Developer_Summit) Videos from the recent OpenZFS developer summit are being uploaded, with speakers from different represented platforms and companies Matt Ahrens (http://www.bsdnow.tv/episodes/2014_05_14-bsdcanned_goods), opening keynote (https://www.youtube.com/watch?v=XnTzbisLYzg) Raphael Carvalho, Platform Overview: ZFS on OSv (https://www.youtube.com/watch?v=TJLOBLSRoHE) Brian Behlendorf, Platform Overview: ZFS on Linux (https://www.youtube.com/watch?v=_MVOpMNV7LY) Prakash Surya, Platform Overview: illumos (https://www.youtube.com/watch?v=UtlGt3ag0o0) Xin Li, Platform Overview: FreeBSD (https://www.youtube.com/watch?v=xO0x5_3A1X4) All platforms, Group Q&A Session (https://www.youtube.com/watch?v=t4UlT0RmSCc) Dave Pacheco, Manta (https://www.youtube.com/watch?v=BEoCMpdB8WU) Saso Kiselkov, Compression (https://www.youtube.com/watch?v=TZF92taa_us) George Wilson (http://www.bsdnow.tv/episodes/2013_12_04-zettabytes_for_days), Performance (https://www.youtube.com/watch?v=deJc0EMKrM4) Tim Feldman, Host-Aware SMR (https://www.youtube.com/watch?v=b1yqjV8qemU) Pavel Zakharov, Fast File Cloning (https://www.youtube.com/watch?v=-4c4gsLi1LI) The audio is pretty poor (https://twitter.com/OpenZFS/status/534005125853888512) on all of them unfortunately *** BSDTalk 248 (http://bsdtalk.blogspot.com/2014/11/bsdtalk248-dragonflybsd-with-matthew.html) Our friend Will Backman is still busy getting BSD interviews as well This time he sits down with Matthew Dillon, the lead developer of DragonFly BSD We've never had Dillon on the show, so you'll definitely want to give this one a listen They mainly discuss all the big changes coming in DragonFly's upcoming 4.0 release *** MeetBSD 2014 videos (https://www.meetbsd.com/) The presentations from this year's MeetBSD conference are starting to appear online as well Kirk McKusick (http://www.bsdnow.tv/episodes/2013-10-02_stacks_of_cache), A Narrative History of BSD (https://www.youtube.com/watch?v=DEEr6dT-4uQ) Jordan Hubbard (http://www.bsdnow.tv/episodes/2013_11_27-bridging_the_gap), FreeBSD: The Next 10 Years (https://www.youtube.com/watch?v=Mri66Uz6-8Y) Brendan Gregg, Performance Analysis (https://www.youtube.com/watch?v=uvKMptfXtdo) The slides can be found here (https://www.meetbsd.com/agenda/) *** Feedback/Questions Dominik writes in (http://slexy.org/view/s20PXjp55N) Steven writes in (http://slexy.org/view/s2LwEYT3bA) Florian writes in (http://slexy.org/view/s2ubK8vQVt) Richard writes in (http://slexy.org/view/s216Eq8nFG) Kevin writes in (http://slexy.org/view/s21D2ugDUy) *** Mailing List Gold Contributing without code (https://www.marc.info/?t=141600819500004&r=1&w=2) Compression isn't a CRIME (https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-November/033176.html) Securing web browsers (https://www.marc.info/?t=141616714600001&r=1&w=2) ***