[-] [email protected] 7 points 5 days ago

It's not about user-led synergy. The personal data market is slurped up by those that already have and are building correlations. Just because a user didn't report anything to their insurer doesn't mean an insurer sure as shit isn't going to want the data if they can link it to the user whatsoever, so long as it will make them more money.

This is hypothetical, of course, but it's the way the market of data brokers works.

[-] [email protected] 15 points 5 days ago

You joke, but I guarantee there's a market. Consider health insurance companies that see an opportunity to charge everyone more unless they can prove their good brushing habits via app data.

[-] [email protected] 1 points 6 days ago

Options are great, this is what drives the Linux community to come up with great solutions!

That said... Kate is an easy winner for me.

22
submitted 1 month ago by [email protected] to c/[email protected]
0
submitted 1 month ago by [email protected] to c/[email protected]
[-] [email protected] 16 points 1 month ago

They misspelled "backdoors."

10
submitted 1 month ago by [email protected] to c/[email protected]
60
submitted 1 month ago by [email protected] to c/[email protected]

This one is less focused on self-hosting a homelab service, but I thought might be interesting for the homelabbers here. I got into this hobby through my career in cybersecurity, and decided to write up a little post about a tool I frequently use, mitmproxy!

[-] [email protected] 15 points 1 month ago

I love avocados, but can't say I've ever liquified them then drizzle on toast...

4
submitted 1 month ago by [email protected] to c/[email protected]

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

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.

89
submitted 1 month ago by [email protected] to c/[email protected]

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.

18
submitted 2 months ago by [email protected] to c/[email protected]

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!

100
submitted 2 months ago by [email protected] to c/[email protected]

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

52
submitted 2 months ago by [email protected] to c/[email protected]

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.

6
submitted 2 months ago by [email protected] to c/[email protected]

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!

73
submitted 2 months ago by [email protected] to c/[email protected]

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!

4
submitted 2 months ago by [email protected] to c/[email protected]

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.

[-] [email protected] 12 points 3 months ago

I thought this was gonna be some animorphs shenanigans from the thumbnail

[-] [email protected] 110 points 1 year ago

It's just an NTP pool. The device is trying to update it's time. Likely it made many other requests to other servers when this one didn't work.

Maintaining up to date lists of anything is a game of whack a mole, so you're always going to get weird results.

If you're actually unsure, pcap the traffic on your pfsense box and see for yourself. NTP is an unencrypted protocol, so tshark or Wireshark will have no problem telling you all about it.

That said, I'd still agree with the other poster about local integration with home assistant and just block that sucker from the Internet.

[-] [email protected] 16 points 2 years ago

If you have any question on truth worthiness, you can flash stock openwrt on them. You just lose out on their proprietary webUI and pre installed plugins. I believe their firmware is public on GitHub though.

[-] [email protected] 13 points 2 years ago

That all sounds correct to me. The random port you're seeing in the logs is a high port, often referred to as an ephemeral port, and it is common for source ports. All good there.

[-] [email protected] 34 points 2 years ago

This is pedantic, but there are indeed capacitors there. They're all surface mount components, so they don't look like the caps that people typically talk about replacing, and they likely aren't what caused it to fail. Anything labeled on the board with a C## is likely a SMD capacitor.

[-] [email protected] 12 points 2 years ago

😆 God the judiciary is fucked up...

view more: next ›

starkzarn

0 post score
0 comment score
joined 2 years ago