What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

お知らせ📣
「ねがいぼしのエトワール」がぬいぐるみになりました!
コンプセットは500円引き、先着30名様には描き下ろしサイン入りポストカード付き!
ぜひお迎えしていただけると嬉しいです
🌟(グッズ単体もあります)

販売期間【12月17日〜1月13日】
ご購入はこちら
⬇️
https://lastrologie.stores.jp

1
1
0
0
0
0
1
1

Q: 서버실의 여우들에게 안부 전해주세요 #neo_quesdon

A: 여우의 답변입니다.

도중에 본 메시지라 답변이 늦어졌네요!
와서 한번 유부초밥이라도 한끼 하자고 말씀드리고싶지만...
주간점검이 아직 끝나지 않아 이번주는 어렵겠네요
세달~네달 이내로 시간이 날진 모르겠지만
요전번에 단장님이 휴가를 줬으니 시간이 날지도 몰라요! 고마워요!

라네요.
https://neo-quesdon.serafuku.moe/main/user/@Villain_jud@kitsunesoba.com/cmj9w94gd3eylo60jecyd98m2

0
1
1
흑백2 잠깐 본 소감 : 또 CJ인가? 선재스님 멋지다. 랜선 도화살, 조림의 신 교토음식이 최고라고 🇯🇵에서 가장 잘나가는 오사카사람 앞이서 말해버린 기개넘치는 최강로꾸님은 어디까지 올라갈까?
0
0
0
0
0
0
1
0
1
0
1
0
1
0

Good morning Fedi friends!

Feeling a little emotional today as I reflect back on one year of #selfhosting.

This toot from December 17 2024 shows off my excitement over signing up for my first VPS and installing #YunoHost: https://mastodon.social/@_elena/113667636910565210

If you check out the full thread you can see some of the challenges I faced in the early days. It's only been a year but it feels like a lifetime ago. When I read back, I think: who was this person? _ (task) is so easy! Like, why be scared of tweaking DNS records? 😅​

I will write about the highs and lows in a proper blog post. Spoiler alert: there were mostly HIGHS ☺️​

For now, I want to express my gratitude to:

✨​ @shollyethanEthan Sholly who encouraged me by saying (I'm paraphrasing) "go for it, you learn by doing things"

✨​ @iljailja :pumpkin_owo: who recommended I check out YunoHost (I had never heard of it before)

:YunoHost:​@yunohost@toot.aquilenet.fr for empowering me to self-host so many great FOSS tools... and upgrading and maintaining them in a super easy way

@stereoralf tauscher :FreiburgSocial: for helping me test my first self-hosted app (this #GoToSocial account)

And thank you to all the sysadmins and programmers who have helped me troubleshoot problems this year. I found that tech support on the Fediverse takes less than a minute 🥰​​

I'm really #GratefulForYou 💖​

#MySoCalledSudoLife

0
3
0
0
1
1
0
0
0
1
1
1
0
0
원래(?) 계획은 부-울-경을 하나의 메가시티로 묶고, 광역 교통망+부도심권을 찍고 통합창원시(마창진)를 서울 가준 용인-수원-화성 포지션으로 하려고 했는데...
그런건 모르겠고 ​:apt_rose:​만 외치더니...
0
0
2
0
0
0
0
0
1
0
0

OpenSSH runs a large number of tests via Github Runners, both Github supplied ones on a public repo, and on selfhosted runners on a private repo. The latter covers a bunch of platforms Github doesn't support, and is private not because we don't want it accessible (in fact we would prefer it be public) but because as far as we can tell, making it public would represent a significant security risk.

Github have announced that they will begin charging per-minute fees for Github Actions self-hosted runners starting next year. These fees apply only to runners on private repos, but "actions will remain free in public repositories."[0] This is going to be a significant problem for us.

Github's own documentation points out allowing selfhosted runners on public repositories is unsafe, because it's a potential remote code execution vector via running arbitrary workflows in modified pull requests:

"As a result, self-hosted runners should almost never be used for public repositories on GitHub, because any user can open pull requests against the repository and compromise the environment."[2]

There are some controls[1], but the documentation on them doesn't exactly instill confidence (emphasis on the weasel words added):

"Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's GitHub Actions workflows. [...] To *help* prevent this, workflows on pull requests to public repositories from *some* outside contributors will not run automatically, and *might* need to be approved first. Depending on the "Approval for running fork pull request workflows from contributors" setting, workflows on pull requests to public repositories will not run automatically and *may* need approval if: The pull request is created by a user that requires approvals based on the selected policy.[or] The pull request event is triggered by a user that requires approvals based on the selected policy."

All of this uncertainty could be addressed by completely disabling pull requests on a repo, but while that has been requested many many times over the course of a decade([3] [4]), this is still not possible.

It *is* possble to *temporarily* disable pull requests on a repository via Interaction Limits[5], but using this as a security control that (silently?) fails open after some amount of time is problematic to say the least. The required functionality is almost there, it just needs a "forever" option.

So, in summary: self-hosted runners remain free as long as you run them on public repos, which you shouldn't because it's unsafe, unless you also disable pull requests, which you probably can't.

[0] resources.github.com/actions/2
[1] docs.github.com/en/repositorie
[2] docs.github.com/en/actions/ref
[3] github.com/orgs/community/disc
[4] github.com/dear-github/dear-gi
[5] docs.github.com/en/communities

0
0
0
0
1

3Dプリンターですら山寨機が登場しているのが機体に違わぬ中国らしさ。品質がそこまででもない機械を送り出して訴訟に巻き込まれたりしないんだろうか。うまい免責条項を仕込むような専門家が存在する?
- シェア9割越え。家庭用3Dプリンター市場を中国勢が制した理由 | レバテックラボ(レバテックLAB) levtech.jp/media/article/colum

0