z0rs

Red Teaming tool

• General usefull Powershell Scripts
• AMSI Bypass restriction Bypass
• Payload Hosting
• Network Share Scanner
• Lateral Movement
• Reverse Shellz
• POST Exploitation

quad

I've been writing Rust full-time with a small team for over a year now. Throughout, I've lamented the lack of clear best practices around defining error types. One day, I'd love to write up my journey and enumerate the various strategies I've both seen and tried. Today is not that day.

Today, I want to reply to a blog post that almost perfectly summarised my current practice.

Go read it; I'll wait!

---

sharadhr

$HOME, Not So Sweet $HOME

• Preface
• 1 What is $HOME to you?
• 2 Setup
  • 2.1 Linux
    • 2.1.1 $HOME
    • 2.1.2 Dot-files and dot-directories
    • 2.1.3 XDG Base Directories
• 2.1.4 xdg-user-dirs

luca992

use snafu::Snafu;

/// Error type for all API traits
/// Note: Do not put implementation specific errors here (so no errors from reqwest, serde, etc.)
/// These should be generic errors that can be used by any API implementation.
/// The implementation specific errors should be defined locally for each API implementation then
/// converted to this error type before being returned.
///
/// Hint: use [From] to convert implementation specific errors to this error type. You can define
/// an error snafu enum inside the same file as an api implementation and also implement the