noUsernamesLef7

joined 1 year ago
[–] [email protected] 1 points 9 months ago (1 children)

You make it sound as if it's a thing of the past when it is still a common problem.

[–] [email protected] 1 points 9 months ago (3 children)

And yet injection is still #3 in the OWASP Top 10

[–] [email protected] 2 points 9 months ago

This article is AI generated SEO spam.

[–] [email protected] 2 points 9 months ago

I set up Netbox recently at work to try and improve the abysmal documentation situation. I use an Ansible playbook to provision and set up the server, then copy a docker compose file and start the containers. So far I'm loving Netbox, I just wish my predecessors had documented things from the start.

[–] [email protected] 3 points 9 months ago

Namecheap + the dynamic DNS client in pfSense. No issues sinve I set it up years ago.

Before that it was a cron job that updated through the google domains api.

[–] [email protected] 3 points 9 months ago

Da Archive maybe? Most of my stuff has come from there.

[–] [email protected] 5 points 9 months ago (1 children)

I recently set up and started using MediaTracker for this purpose. It's kind of barebones, but functional. Seems like its biggest difference with movary is that it also covers TV, ebooks, audiobooks, and games.

I have a little section for movies and books on my website and i've been working on a script to automatically pull those lists and reviews from MediaTrackers api each time I build my site.

[–] [email protected] 4 points 9 months ago

Stay suspicious. As a security guy, i'd way rather respond to 1,000 false positive reports than have an employee that doesn't think about it and just clicks.

[–] [email protected] 3 points 9 months ago

It is a great step but it's rare to have enough buy in from upper managent to enforce any real consequences for repeat offenders. I've seen good initial results from this kind of phishing testing, but the repeat offenders never seem to change their habits and your click rate quickly plateaus.

[–] [email protected] 2 points 9 months ago

A little late, but here is what I usually do when a ticket like that comes in:

  1. Check monitoring. It's quick and easy to check so I'll look before even asking any clarifying questions. If there is a real network problem at a site, 95% of the time its going to show up on our monitoring dashboard. Everything from ISP outages to device failures show up here.
  2. Ask for more details about what they are trying to do. What is the goal? What are you doing? What is happening? What should be happening? When was the last time it worked?
  3. Based on those details, I can usually put together a good guess as to what might be going on, so i'll test that theory out and see if i'm right.
[–] [email protected] 1 points 10 months ago

Oh thanks, saved. Will break this image out next time it happens, though I usually end up dying from getting into desperate situations looking for antifungals before it gets to this point.

[–] [email protected] 3 points 10 months ago

Thanks! This is actually exactly what I have been basing my efforts on so far, it's just sobering to look at how far away we are from completing implementation group 1.

view more: next ›