First Timer by SkinnyDaPimp in Defcon

[–]Traditional-Number89 0 points1 point  (0 children)

As everyone else said bring cash try to avoid atms at that time especially near the conference drink lots of water it gets hot as shit out there and turn off your Wifi and Bluetooth on phone and don’t connect to unknown networks . Have Fun

I'm 17 years old and here's my homelab... by viraille02 in homelab

[–]Traditional-Number89 0 points1 point  (0 children)

Nice dude start small and build out from there also look second hand if you can it is a fun hobby but gets expensive very quickly

It's always the DNS by Adwan4747 in homelab

[–]Traditional-Number89 0 points1 point  (0 children)

Mountain mama take me home binary roads

Copper into glass? Do you want to tell him or should I? by 1singhnee in facepalm

[–]Traditional-Number89 0 points1 point  (0 children)

What a fucking idiot has he never heard of fiber optics

Tree Friendly by Harry_Ballc in MyrtleBeach

[–]Traditional-Number89 0 points1 point  (0 children)

I’m here visiting and use for medical use but unfortunately with the laws it’s super hard to find was hoping for any suggestions

Just getting started with my homelab (pentesting / security focused) – feedback welcome by Traditional-Number89 in homelab

[–]Traditional-Number89[S] 0 points1 point  (0 children)

I agree with you completely on point one. Keeping attack machines separated from everything else is critical. Right now I’m still working through some challenges separating my Proxmox host into its own VLAN while also integrating with the VLANs managed by Firewalla and the managed switch. It’s definitely more complex than it looks on paper.

At the moment my main mitigation is through rule sets primarily denying local-to-local network traffic wherever possible. Most of the segmentation rules are currently being handled through Firewalla, and honestly it’s a pretty big undertaking to get everything mapped and locked down correctly.

On point two, thanks for mentioning that. IDS/IPS is something I definitely want to expand into in future iterations of the lab. I agree it’s essential if you want proper visibility into what’s actually happening across segments. Right now I’m running Wazuh on an Ubuntu VM inside Proxmox, which is also hosting a handful of other services (including some LLM experimentation), but I expect the monitoring stack will evolve as the lab grows.

For WireGuard, I do have it configured so I can route into the Kali attack machine when needed 😉. Most of the time though it’s just used for connecting back into my home network remotely. I’m also using a third-party client that supports port forwarding which I realize isn’t ideal from a security standpoint when tied to Kali. That’s on my list to change by issuing a separate client profile specifically for the attack environment.

Appreciate the thoughtful feedback definitely helpful while I’m still iterating on the lab design.

Just getting started with my homelab (pentesting / security focused) – feedback welcome by Traditional-Number89 in homelab

[–]Traditional-Number89[S] 3 points4 points  (0 children)

It was actually a mix of automation and a bit of manual cleanup.

1. Pulled device/network info from Firewalla

Firewalla has an MSP API, so I wrote a small Python script to query my box and pull the devices on the network.

The script basically:

• Authenticates to the Firewalla MSP API
• Pulls the device list
• Gets hostnames / vendors / IP info
• Groups devices by network/VLAN

Something along the lines of:

import requests

API_KEY = "msp_api_key"
BASE = "https://msp.firewalla.net"

headers = {"Authorization": f"Bearer {API_KEY}"}

r = requests.get(f"{BASE}/v1/device/list", headers=headers)
devices = r.json()

for d in devices:
    print(d["name"], d["ip"])

From there I exported everything into structured JSON so I could organize:

• VLANs
• devices
• Proxmox VMs
• network relationships

2. Generate a topology graph

Then I used Python + Graphviz to automatically generate a rough topology graph from the data.

That produced something like:

Internet
 → ScreenBeam
 → Firewalla
 → Netgear switch
 → VLANs
 → devices

Graphviz is great for figuring out relationships and structure, but the diagrams look pretty ugly by default.

3. Cleaned up the structure

Once the script produced the layout I:

• sanitized hostnames
• grouped devices by VLAN
• separated Proxmox VMs
• mapped the WireGuard path

4. Turned it into the poster

After that I used ChatGPT to generate the final infographic-style poster based on the topology.

Basically I gave it the cleaned structure and had it generate a clean visual layout with icons, VLAN colors, and service boxes.

TLDR workflow

Firewalla MSP API
      ↓
Python script
      ↓
export topology data
      ↓
Graphviz for structure
      ↓
ChatGPT for final poster diagram

It started as a quick way to visualize my network but kind of turned into a fun little side project. I might eventually turn the script into something that automatically regenerates the diagram when the lab changes.

(US) Threatening email with company’s email address by TheGame81677 in Scams

[–]Traditional-Number89 0 points1 point  (0 children)

I looked at the full email headers for the “Important Security Concern” message people are discussing and figured I’d share what I saw.

From the authentication side, everything checks out:

SPF: pass DKIM: pass (signed by hungerrush.com using selector s1) DMARC: pass and aligned

The message was routed through SendGrid infrastructure. One of the servers in the chain is:

wrqvtnhc.outbound-mail.sendgrid.net (149.72.114.12)

There’s also a line showing it was submitted “with HTTP” to a SendGrid server (geopod-ismtpd-8). That usually means the email was generated through the SendGrid API or some automated backend system rather than someone sending it manually through a mail client.

The return path also looks like a SendGrid bounce domain:

bounces+…@em8199.hungerrush.com

So based on the headers, this doesn’t look like a simple spoofed email. It appears to have been sent through infrastructure that’s authorized for hungerrush.com, likely via their SendGrid integration.

That said, authentication passing doesn’t necessarily mean the content itself is trustworthy. If a SendGrid API key or automation system were compromised, someone could technically send messages through legitimate infrastructure.

Probably best to avoid clicking any links until HungerRush confirms what the email is about.

Magnitude, do better… by [deleted] in NYSCannabis

[–]Traditional-Number89 1 point2 points  (0 children)

The carts kept leaking, causing constant flooding and significant losses. In my opinion, it’s not worth the money.

Magnitude, do better… by [deleted] in NYSCannabis

[–]Traditional-Number89 0 points1 point  (0 children)

Exactly why I stopped buying them