Konto erstellenAnmelden

Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
kif.rocks ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.

Verwaltet von:

Serverstatistik:

160
aktive Profile

kif.rocks: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.3.6

#memorysafety

2 Beiträge2 Beteiligte0 Beiträge heute
Öffentlich *
T_X

#RemiPommarel found and fixed a bug/regression in a recent change someone had added to @batadv in the #Linux #kernel. One take home message from Remi:

"On a side note, I am all about #hardening and #MemorySafety stuff but if that means impacting readability and spending more time trying to please the tool than thinking about the #correctness of the code change, that's where we end up converting a perfectly fine #code into a logically flawed one."
(hash tags added by me)

patchwork.open-mesh.org/projec

patchwork.open-mesh.orgbatman-adv: Fix incorrect offset in batadv_tt_tvlv_ogm_handler_v1() - Patchwork
Öffentlich
Chandler Carruth

Had a bunch of thoughts about the recent safety stuff, way more than fit in social media post... Blog post story time! (It's a bit of a ramble, sorry about that...)

chandlerc.blog/posts/2024/11/s

chandlerc.blog · Story-time: C++, bounds checking, performance, and compilersRecently, several of my colleagues at Google shared the story of how we are retrofitting spatial safety onto our monolithic C++ codebase: https://security.googleblog.com/2024/11/retrofitting-spatial-safety-to-hundreds.html I wanted to have a bit of story-time about some of the strange ways that all this came to be, at least as I remember things. There are some really interesting developments that led us here, and some important lessons to learn from that history. Do note that this is just my retrospective memory. It’s entirely possible I’m misremembering some of it (let me know if so!). It’s also limited to my perspective, and others may have seen very different aspects of things (please share!).
#LLVM#Clang#MemorySafety
Öffentlich
EuroRust

Dive into today’s #eurorust24 talk with @amanda as she unpacks Rust’s Polonius project 🦀 She breaks down how it improves the borrow checker and lifetimes, allowing you to write more correct code in safe Rust, making Rust even better for your projects. Essential watching for anyone curious about Rust's borrow checker evolution.

🎥 Watch here 👉 youtu.be/uCN_LRcswts

YouTubeThe first six years in the development of Polonius - Amanda Stjerna | EuroRust 2024Von EuroRust
#rustlang#memorysafety#compilers
Öffentlich
𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕

Rustls Outperforms OpenSSL and BoringSSL

Rustls is a memory safe TLS implementation with a focus on performance. It is production ready and used in a wide range of applications.

🦀 memorysafety.org/blog/rustls-p

www.memorysafety.org · Rustls Outperforms OpenSSL and BoringSSLISRG has been investing heavily in the Rustls TLS library over the past few years. Our goal is to create a library that is both memory safe and a leader in performance. Back in January of this year we published a post about the start of our performance journey. We've come a long way since then and we're excited to share an update on Rustls performance today. What is Rustls? Rustls is a memory safe TLS implementation with a focus on performance.
#rust#ssl#rustls
Öffentlich
jbz

🔐 C++ Must Become Safer — Andrew Lilley Brinker — Software Supply Chain Security

｢ If a cheap-to-maintain legacy system is faced with the proposition of an expensive rewrite, it may instead be eliminated. The externalities of this kind of change are difficult to consider in advance and in general ｣

alilleybrinker.com/blog/cpp-mu

www.alilleybrinker.comOpen Source Software and Corporate Influence — Andrew Lilley BrinkerOpen source software projects are frequently enmeshed with the interests of corporations. We should update mental models of who works on open source accordingly, and build or modify power structures to be more resilient to corporate capture.
#C#CPP#Rust
Öffentlich
Sebastian Dröge 🍵

It's quite ridiculous that standard C still does not have vasprintf() / asprintf() after Linux and all the BSDs (and macOS) have this since basically forever (but not Windows of course), and wrong use of the non-allocating versions is a quite common cause of security bugs.

Does someone know what happened with TR 24731-2, which would add them? It looks like there has been no progress at all since 2009 while theoretically the addition of these two functions seems like a no-brainer.

Is the conclusion simply that nobody actually needs it anymore because everybody already has their own implementation of it anyway, doesn't target Windows or niche platforms, or uses a safer language?

#c#programming#memorysafety
Öffentlich
tarakiyee

This is a long read, don't click the link before you have your coffee/tea/mountain dew code red/beverage of choice ready!

In this blogpost, I try to explain why we at @sovtechfund are investing in #MemorySafety and reflect a bit on the awe inspiring work of critical infrastructure maintainer partners, as well as where we are at the moment and the long way ahead.

sovereigntechfund.de/news/on-r

Sovereign Tech FundOn Rust, Memory Safety, and Open Source Infrastructure | Sovereign…
Öffentlich *
Sovereign Tech Agency

Addressing #memorysafety in critical infrastructure is a complex issue with multiple approaches. The Sovereign Tech Fund supports several initiatives, and technologist @tarakiyee reflects on the long road ahead in a blog post “On Rust, Memory Safety, and Open Source Infrastructure”

sovereigntechfund.de/news/on-r

Sovereign Tech FundOn Rust, Memory Safety, and Open Source Infrastructure | Sovereign…
EntdeckenLive-Feeds
Über