jerry

joined 3 years ago
MODERATOR OF
securitynews
infosecpub
testing
sorted by: new top controversial old
Congress Just Snuck In Uber Immunity in c/politics@lemmy.world
[–] jerry@infosec.pub 4 points 5 days 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@infosec.pub
[–] jerry@infosec.pub 3 points 5 days ago

sorry for the trouble.

Lack of content - are we not federated? in c/infosecpub@infosec.pub
15
Federation issue and image issue should be fixed now. (infosec.pub)
 

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@infosec.pub
[–] jerry@infosec.pub 3 points 5 days 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@infosec.pub 3 points 5 days 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@infosec.pub
[–] jerry@infosec.pub 6 points 5 days 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@infosec.pub
Congress Just Snuck In Uber Immunity in c/politics@lemmy.world
[–] jerry@infosec.pub 6 points 5 days 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.

4
Anonymous access to infosec.pub is disabled temporarily (infosec.pub)
 

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.

Some images are broken in c/infosecpub@infosec.pub
[–] jerry@infosec.pub 1 points 9 months ago

The problem is with the image storage engine, pict-rs. So far, the documented configurations that should fix that haven't worked. In the mean time, I've disabled image proxying, which should prevent the error.

Some images are broken in c/infosecpub@infosec.pub
[–] jerry@infosec.pub 1 points 9 months ago

Thanks. I am trying to sort out what is wrong

Welcome to the new home of what was /r/Blueteamsec and how it works.. in c/blueteamsec@infosec.pub
[–] jerry@infosec.pub 2 points 10 months ago

I unpinned it. Apologies for leaving it at the top for so long

Some images are broken in c/infosecpub@infosec.pub
[–] jerry@infosec.pub 1 points 11 months ago (3 children)

Thanks for the report. I’ll investigate

8
Tesseract and Voyager interfaces now available (infosec.pub)
submitted 1 year ago* (last edited 1 year ago) by jerry@infosec.pub to c/infosecpub@infosec.pub
4 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 (infosec.pub)
 

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.

13
Introducing old.infosec.pub (infosec.pub)
 

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 (infosec.pub)
submitted 1 year ago* (last edited 1 year ago) by jerry@infosec.pub to c/infosecpub@infosec.pub
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 (infosec.pub)
 

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 (infosec.pub)
 

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 (infosec.pub)
 

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 (infosec.pub)
 

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 (infosec.pub)
 

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

31
Infosec.pub scheduled downtime (infosec.pub)
 

Infosec.pub will be down for maintenance on Monday, July 1 2024, from approximately 10am until 1pm Eastern Time. I will be upgrading to the latest version of Lemmy, which requires an upgrade to postgres.

view more: next ›