𝘴𝘦𝘵𝘤𝘩𝘪܀

「進研ゼミ小学講座」で配信中の SF ドラマ『情報発信局「わくわく! 地球調査隊」』についての記事が公開されました！ 私が開発している Furigana Studio を字幕制作に採用したエピソードにも触れていただきました。 #進研ゼミ #小学講座

9年ぶりにダイオウグソクムシの3Dペーパーパズルを組み立てた。柄があることでパーツごとに「裏表」の概念が発生してめんどくささ UP してた😂 かわいい〜

山中湖🗻

サイコー‼️

水深8m

泊まる宿は安めでも、お風呂だけちょっと良い宿の日帰り温泉を使うと満足度が高いし宿の雰囲気も見れて下見にもなるしイイネ

Philips PicoPix Max 、800 ANSI 「Color」 Lumensで小型の割に画質発色が良いお気に入り携帯プロジェクター‼️ なんの変哲もないビジホでも天井に映せば寝転びながら映画が観れてたのしい✌

大きい水門 海の色がグラデーションしてる

ダイオウグソクムシと、透明骨格標本と、ペーパークラフト（買っちった）

深海の生き物をみてきた

市場とれたて沼津ごはん🐟 後半は出汁でお茶漬けにして二度おいしい

昨日は雨だったのもあって宿でズートピア観た プロジェクター持ってってよかったね 最速のフラッシュが好きすぎる

最高の旅

🐟🐟🐟

‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP. The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years. Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box. The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root. Result: the next time anyone runs that program, it lets the attacker in as root. What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk. Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants. The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today. This vulnerability affects the following: 🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root 🔴 Kubernetes and container clusters: one compromised pod escapes to the host 🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner 🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root Timeline: 🔴 March 23, 2026: reported to the Linux kernel security team 🔴 April 1: patch committed to mainline (commit a664bf3d603d) 🔴 April 22: CVE assigned 🔴 April 29: public disclosure Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module: echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 2>/dev/null || true For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...

ソニーのFreFlowですね。 照明の制御に使われるDMX信号を特小帯920MHzのRF信号に変換、ペンライトに送信して点灯制御。 観客はスマホで客席のQRコードを読取りBluetoothを介してペンラに座席番号を登録することで、より精密な制御が可能になっている。 制御可能台数は無制限。 sonymusicsolutions.co.jp/s/sms/diary/de…

「趣味」をやっているのか「見栄のための消費」をしているのかぐらいは区別しときたいよな

趣味そのものに魅了された結果承認が伴う人は楽しそうだけど、最初から趣味を媒介した承認に依存してる人はなんか苦しそう 自転車乗るのにモチベーションとか考えない人は多分前者

黄ばみ散らかしたカーボンホイール、かわええ🤤

Once @wiz_io disclosed, we validated the finding, deployed a fix to github(.)com, and confirmed there was no exploitation in less than two hours. Read more about what happened, how we responded, and what we are doing to prevent similar issues in the future. ⬇️ github.blog/security/secur…