starkzarn

joined 2 years ago
[–] starkzarn 4 points 3 weeks ago (4 children)

Yeah they just redid their container image pipeline and these containers are the result!

[–] starkzarn 5 points 3 weeks ago

Super true. I think this was best exemplified by SignalGate

[–] starkzarn 7 points 3 weeks ago (9 children)

This is great, I have not seen this post before. Thank you for sharing.

You make an excellent point here, that the burden of security and privacy is put on the user, and that means that the other party in which you're engaged in conversation with can mess it up for the both of you. It's far from perfect, absolutely. Ideally you can educate those that are willing to chat with you on XMPP and kill two birds with one stone, good E2EE, and security and privacy training for a friend. XMPP doesn't tick the same box as Signal though, certainly. I still rely heavily on Signal, but that data resides on and transits a lot of things that I don't control. There's a time and a place for concerns with both, but I wanted to share my strategy for an internal chat server that also meets some of those privacy and security wickets.

[–] starkzarn 4 points 3 weeks ago

Yes, absolutely. It all depends on implementation. I am using VLANs for L2 isolation. I have a specific DMZ VLAN that has my XMPP server and only my XMPP server on it. My network core applies ACLs that prevent any inter-VLAN traffic from there, so even if STUN/TURN pokes holes, the most that is accessible is that single VLAN, which happens to contain only the single host that I want to be accessible.

Great question.

[–] starkzarn 2 points 3 weeks ago

Just updated my original comment, but that XMPP blog post I mentioned is live: https://roguesecurity.dev/blog/xmpp

[–] starkzarn 2 points 3 weeks ago (2 children)
[–] starkzarn 6 points 3 weeks ago

Arch wiki never fails to deliver!

[–] starkzarn 41 points 3 weeks ago* (last edited 3 weeks ago) (5 children)

XMPP most definitely! Especially if you want to have connectivity to other servers at all (like simplex). It's much simpler, more well-known, battle hardened, and still supports E2EE and video calling very well.

I recommend prosody. I recently went through the process of setting up a server and have a draft blog on it half way finished if you want an account of the experience.

EDIT: Blog post is live at https://roguesecurity.dev/blog/xmpp

[–] starkzarn 1 points 1 month ago

There is not a mobile app, no. You can pseudo install it as a PWA if using a chromium based browser though.

I do use HomeAssistant so I let it do the notifications for me, but you could easily setup pubsub and use that to hook gotify or something. Maybe it even has native webhooks at this point, I'm not sure.

Notably though I don't run frigate in HomeAssistant, it's just plugged in via API. That's to support hardware passthrough for my coral TPU.

I highly recommend it over the others. the only one I haven't tested is blue iris because it's windows only and I refuse to have a windows machine on my network. Frigate outperforms all the others that I tested. Zoneminder is a runner up but it feels dated and the object detection is a kludge.

[–] starkzarn 4 points 1 month ago

Fantastic writeup. Thank you!

[–] starkzarn 3 points 1 month ago (2 children)

I have some reolink and some amcrest, and I'd choose the amcrest (or dahua) any day tbh. Similar workload. Tensor and frigate for software NVR and object detection, all to a zfs dataset.

[–] starkzarn 2 points 1 month ago

Says who? I give all my billionaire best friends shit every day.

 

If you've followed any of my self-hosted headscale with Podman series, I wrote up another "bonus" post talking about OIDC configuration with Authelia. Took some trial and error, so I figured I'd document it in the public notebook.

 

cross-posted from: https://infosec.pub/post/28196930

Another post in the records for the tech blog, this time all about opensource network monitoring with LibreNMS!

 

Another post in the records for the tech blog, this time all about opensource network monitoring with LibreNMS!

 

For those that were interested in my PART 1 post of the Grafana Loki OPNSense firewall log monitoring, I present you: PART 2! This one is the good one (albeit less technical) where we get the eye candy after getting the log ingestion pipeline already setup in part 1.

 

cross-posted from: https://infosec.pub/post/27200076

My first blog series on headscale with traefik through podman quadlets was pretty well received on here. I'm just getting started with this blog, and thought the second topic I recently worked on might be popular in this crowd too: a lower resource method of centralizing logs for OPNSense with Grafana Loki (and Alloy) including geoIP!

 

My first blog series on headscale with traefik through podman quadlets was pretty well received on here. I'm just getting started with this blog, and thought the second topic I recently worked on might be popular in this crowd too: a lower resource method of centralizing logs for OPNSense with Grafana Loki (and Alloy) including geoIP!

 

About a month ago I switched from Google Fi to Mint Mobile. I figured since they were both T-Mobile MVNOs the service would the same, and it was a way for me to move away from the Google Fi app requirement, and this the play services requirement on my graphene pixel 8 pro. Everything initially seemed to be working great, then I realized I only ever have LTE. I've tried all the APN settings, auto discovered, manually configured in accordance with the mint documentation, and the T-Mobile APN. They all give me good service, but only ever LTE. Previously on both T-Mobile and Fi, on the same cell towers, I had 5g, so I know it's not a service issue. Mint support is the worst thing I've ever encountered in my life and they're useless as far as troubleshooting. Notably, the other phone on the plan is a stock pixel 7 pro and has the same issue, so I think it's a provisioning issue not a graphene issue, but I figured I'd ask the crowd here because of the general level of aptitude.

 

Part 1 of my Headscale and Traefik blog post seems to have gotten some good traction, so I just wanted to share with the community that I just published part 2!

 

Shameless self-plug here. I wrote a blog post to document my methodology after having some issues with publicly available examples of using Podman and traefik in a best-practices config. Hopefully this finds the one other person that was in my shoes and helps them out. Super happy for feedback if others care to share.

view more: ‹ prev next ›