eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

218
active users

#rustlang

48 posts38 participants1 post today

New Open-Source Tool Spotlight 🚨🚨🚨

Groundhog by @ghuntley explains AI coding agents like Cursor from first principles. Built in Rust, it teaches the inner workings of coding assistants—perfect for learning or building your own. #AI #RustLang

🔗 Project link on #GitHub 👉 github.com/ghuntley/groundhog

#Infosec #Cybersecurity #Software #Technology #News #CTF #Cybersecuritycareer #hacking #redteam #blueteam #purpleteam #tips #opensource #cloudsecurity

✨
🔐 P.S. Found this helpful? Tap Follow for more cybersecurity tips and insights! I share weekly content for professionals and people who want to get into cyber. Happy hacking 💻🏴‍☠️

We're proud to launch "dnst", our #DNS toolbox for network operators. Twenty years ago, we introduced the "ldns" C-library, along with a collection of example utilities for generating keys, signing a zone, and more. With the "domain" #Rust crate acting as the natural successor to the "ldns" library, with "dnst" we are offering a modern, well-maintained drop-in replacement for the most widely used "ldns" utilities. #OpenSource #rustlang blog.nlnetlabs.nl/introducing-

The NLnet Labs Blog · Introducing dnst — a DNS Toolbox for network operatorsBy Alex Band More than two decades ago, NLnet Labs started the ldns library, with the goal of letting developers easily create RFC compliant DNS software in the C programming language. The library included a number of example programs, many of which have found their way into operator workflows. With
Replied to Rust Weekly 🦀

@rust_discussions
"... it's clear to me that using Rust allows me to write more correct code and makes me happier compared to dealing with C++."

This is actually the reason I got in to #rustlang . I needed to interact with some specific hardware using some C-libraries. Thinking "there must be a better language for this than C/C++" I wrapped the lib using rust and bindgen. And I was right, there was a better language than C/C++ for that.

Fellow Rustaceans, what/how should the lifetimes look for an upward arg? I'm trying to make an HTTP and return a reader. Or should I use an out parameter for scenarios like this instead?

```rust
use ureq::BodyReader;
pub fn fetch_feed(channel_id: String) -> anyhow::Result<&'_ BodyReader<'_>> {
let url = format!("youtube.com/feeds/videos.xml?c{channel_id}");
let res = ureq::get(url).call()?;
Ok(&res.into_body().as_reader())
}
```

Replied in thread

@Viss

... so I'm writing my first #rustlang project and need a security mechanism. Despite 40 years of coding, I've always relied on properly qualified security people to keep me on the path of righteousness.

This time I don't have that person.

So fuck it, I'm writing a YubiKey physical key solution.