overview for jerry

Anonymous access to infosec.pub is disabled temporarily in c/infosecpub

[–] jerry 1 points 11 hours ago (1 children)

I think it is because I disabled anonymous access due to the AI scrapers continuously causing the instance to crash. I just reenabled anonymous access which should allow it to be indexed by those sites, but it may cause some instability

Hetzner prices have skyrocketed (up to 3x); how will this affect your Fediverse server? in c/fediverse@lemmy.world

[–] jerry 33 points 2 months ago (1 children)

There was a big price increase a month or two ago that affected existing servers. I think this is recognizing that Hetzner just can’t acquire new servers (particularly memory) at anywhere close to what they could before. RAM prices are up about 400% in the past year and rising, and I think even server chassis and CPUs are being largely soaked up by the mesoscale datacenter builds.

Net net, this sucks. And my expectation is that Hetzner will still be the cheapest game in town by about the same percentages as before. It the costs keep going up, I think we will see the fediverse starting to struggle.

Between the absolute crush of bot registrations and the spiraling costs, I have been contemplating moving to a required donation for new accounts.

Congress Just Snuck In Uber Immunity in c/politics@lemmy.world

[–] jerry 4 points 2 months ago (1 children)

Turns out that wasn't the problem. The problem was a bug in the lemmy release. I've been able to get that fixed now, though

Lack of content - are we not federated? in c/infosecpub

[–] jerry 4 points 2 months ago

sorry for the trouble.

Lack of content - are we not federated? in c/infosecpub

[–] jerry 4 points 2 months ago

see this post: https://infosec.pub/post/47820717

19

Federation issue and image issue should be fixed now. (self.infosecpub)

submitted 2 months ago by jerry to c/infosecpub

2 comments fedilink

Federation broke after I upgraded to lemmy 0.19.19 (I tend to apply security updates relatively fast). Unfortunately, that broke federation due to some issues in the release. The issue is described here: https://github.com/LemmyNet/lemmy/issues/6581 - they've not released a fixed version yet, but that was easy enough to sort out manually.

There was also an image issue. I don't know what happened there, but imagemagick was consistently failing - once I restarted the containers, that problem seems to have gone away. I don't know if it will return or was something held over from the update - perhaps an unclean restart. I'll keep an eye on it, but let me know if you see it again.

Infosec.pub destroys image quality in c/infosecpub

[–] jerry 4 points 2 months ago

Both the image problem and the issue with comments not coming through should be fixed now.

Congress Just Snuck In Uber Immunity in c/politics@lemmy.world

[–] jerry 3 points 2 months ago (3 children)

ok, I found the problem. The latest version of lemmy required a change to the web server config, which I did, however I neglected to restart the web server so that config change could take effect. D'oh. amateur hour. I'm very sorry about that.

Infosec.pub destroys image quality in c/infosecpub

[–] jerry 7 points 2 months ago

I am not 100% sure why yet, but the process that scales images for storage was repeatedly dying since I applied the latest lemmy update. I just restarted things and it's working now, but I am not sure if it will crash again or if it was a one off due to something not getting restarted correctly after the update - I'll keep an eye on it.

Anonymous access to infosec.pub is disabled temporarily in c/infosecpub

Congress Just Snuck In Uber Immunity in c/politics@lemmy.world

[–] jerry 6 points 2 months ago (5 children)

It seems to have broke after I upgraded to the latest version of lemmy. I will try to figure out why and fix it.

Shai-Hulud: Another Wave and Going Open Source in c/blueteamsec

[–] jerry 1 points 3 months ago

This has the potential to be very, very bad

Cyber security pros missing out on pay raises compared to other tech fields in c/blueteamsec

[–] jerry 3 points 4 months ago (1 children)

Exactly. I’ve worked in the security field for a long long time and have come to realize it’s viewed by most companies as a utility like power and water and trash pick up. If it’s not working, people notice and get quite angry, and if it is working, they get mad at how much it costs.

19

Cyber security pros missing out on pay raises compared to other tech fields (www.personneltoday.com)

submitted 4 months ago by jerry to c/blueteamsec

3 comments fedilink

56

Anonymous access to infosec.pub is disabled temporarily (self.infosecpub)

submitted 4 months ago by jerry to c/infosecpub

12 comments fedilink

Scrapers are getting so bad that the lemmy containers are falling over, so I've disabled anonymous access to allow legit users to continue using the service. I will work on improving filtering so I can reenable anonymous access. Apologies for the inconvenience.

10

Tesseract and Voyager interfaces now available (self.infosecpub)

submitted 1 year ago* (last edited 1 year ago) by jerry to c/infosecpub

6 comments fedilink

I set up tesseract (https://t.infosec.pub/) and voyager (https://v.infosec.pub/) in addition to the existing https://old.infosec.pub/.

43

Fair warning about vote manipulation (self.infosecpub)

submitted 1 year ago by jerry to c/infosecpub

8 comments fedilink

I have no idea why this is a thing, but it’s come to my attention that there are several accounts here that are engaging in vote manipulation. This is fair warning that if it continues, I’ll be suspending the accounts involved.

14

Introducing old.infosec.pub (self.infosecpub)

submitted 2 years ago by jerry to c/infosecpub

7 comments fedilink

Hi all. As requested, I just added the mlmym interface to infosec.pub. It approximates the old style reddit interface.

So far, it has some.... quirks. For example, as far as I can tell, you cannot post with an "undetermined" language.

13

Upgrade complete. Infosec.pub downtime/upgrade (self.infosecpub)

submitted 2 years ago* (last edited 2 years ago) by jerry to c/infosecpub

1 comments fedilink

Hi all. Lemmy 0.19.9 released today and it has some fixes I want to get in place sooner rather than later. I will be installing the upgrade in about an hour. The downtime should be minimal, but it’s also possible it goes horribly wrong and I have to run a recovery.

Edit: the upgrade is complete. It was quite painless.

9

infosec.pub downtime - December 14 (self.infosecpub)

submitted 2 years ago by jerry to c/infosecpub

1 comments fedilink

The following instances will be offline briefly on Saturday, December 14 from 9am ET / 2pm UTC for approxmately 10 minutes: infosec.exchange infosec.town infosec.pub pixel.infosec.exchange books.infosec.exchange matrix/element.infosec.exchange relay.infosec.exchange meetup.infosec.exchange video.infosec.exchange infosec.press infosec.place fedia.io fedia.social elk,.infosec.exchange infosec.space convo.casa

The servers supporting these instances require a reboot. The Dell servers these instances run on take a very long time to boot, so I am estimating 10 minutes of downtime. It could be more, could be less.

We use live patches to minimize reboots needed for patching, however Ubuntu only provides livepatch support for a year, which is how long most of these systems have been running for.

9

Call for moderators (self.foss)

submitted 2 years ago by jerry to c/foss

2 comments fedilink

Hi all. This community was created for a spambot (tuxbot) but it appears to have some following. Is anyone interested in moderating the community?

28

Infosec.pub upgrade to lemmy 0.19.6 complete (self.infosecpub)

submitted 2 years ago by jerry to c/infosecpub

1 comments fedilink

The upgrade went smoothly and took less time than I expected. Let me know if any problems. And yes, tuxbot is still suspended.

17

Infosec.pub downtime (self.infosecpub)

submitted 2 years ago by jerry to c/infosecpub

6 comments fedilink

Hello everyone. Lemmy 0.19.6 was released today. I am going to apply the update Sunday, November 10 at 2am UTC. Downtime should not be more than one hour.

1

test (self.test)

submitted 2 years ago by jerry to c/test

2 comments fedilink

@jerry@infosec.exchange @jb2@mastodon.social