Cellularhacker 💜🧪 retweeted
제가 Daum에서 오픈한 API 서비스 중, 가장 자랑스러운 것 중 하나가 '개발자를 위한 우편번호 조회 서비스'였는데요. 이제 12년이 흘러서, 라이브러리 호스팅 도메인을 교체해야 하나 보네요. Daum과 Kakao 도메인 분리 때문인것 같습니다. 오랜 기간 하위호환성을 유지해왔지만, 개발 유지 보수가 안되는 사이트를 위해서, 아예 일반 사용자에게 공지를 해야 하나 봅니다. 이 공지가 보이는 웹 사이트는 11월말까지 수정하시기 바랍니다. 🤣
구. Daum 우편번호 조회 서비스가 제공 되기 전까지는, 개별 웹 사이트 회원 가입 시, 우편 번호 검색 기능은 구현도 유지보수도 만만치 않았습니다. 매번 업데이트 되는 우편 번호, 새로 추가되는 주소, 지번 주소와 도로명 주소 등등... 그동안 개발자들의 수고를 많이 덜어주었을 뿐만 아니라 국민 편익에 상당히 영향을 주었습니다. 앞으로도 중단되지 않고 계속해서 서비스를 제공해 주었으면 하는 바램이네요.
Cellularhacker 💜🧪 retweeted
우리 이혁중 CISO님이 이번에도 아주 좋은 글을 올려주셨네요.
첨언하면, 2006년 초기 망분리 도입시 선진국식의 '데이터 중요도 기반 망분리(지금의 N2SF)'를 도입했었더라면 어땠을까 하는 생각도 듭니다. 당시 일선에서 데이터분류를 잘못할수 있다는 불안감, 간급히 대책을 세워야 한다는 다급함 등이 '획일적 망분리'를 등장시켰고, 그것이 결국에는 SaaS 활용, 클라우드 기반 보안관제 등 보안의 고도화를 너무나도 오랫동안 막고 있었던.... 그 댓가를 우린 지금 치루고 있구요.
[이혁중 CISO 칼럼] 망분리 이후의 망분리: AI 시대 금융보안의 다음 질문 dailysecu.com/news/articleVi…
Cellularhacker 💜🧪 retweeted
Block bots in 10 lines of code. No captchas, no friction for real customers. Sign up for free.
Cellularhacker 💜🧪 retweeted
夏休みの絵日記です。
#ホロわちゃ学園祭_DAY2
Cellularhacker 💜🧪 retweeted
What's happening at Microsoft isn't a surprise at all. When it comes to H1B abuse, they are the worst. I am Asian and when I worked there, all the employees who weren't Indian were treated badly. Guys who spent decades building and maintaining key infra where booted out and replaced by AI and an AI (actual Indian). This is like handing a chimp a machine gun.
They have no idea what they are doing, they have no idea what the slop they copy paste does, they have no clue how old systems work, and carefully built systems over decades were degraded by people who I don't think are actually even engineers.
When I conducted interviews, almost 50% of the Indian applicants had fake degrees. We even had one guy who was hired (3/5 people were Indian and all voted yes against me and the white guy) as a Senior DevOps engineer who was a chef back in India, and ended up faking a bunch of credentials to become a H1B. He paid someone to take all his interviews. He only got caught because on day one, he was making IT tickets asking how to turn on his laptop.
For Indians, the only thing that matters when it comes to hiring is caste. Are you a Brahmin? That's all that matters to them. They push out, bully and overwhelm every other race. There are many large companies now that operate like this. Expect major outages for key services, your data leaked non-stop and zero support for trying to get a service you pay for to work.
Welcome to the new world of tech.
Cellularhacker 💜🧪 retweeted
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them.
Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem.
What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix.
Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited.
The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked.
But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns.
Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it.
I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't.
Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
Cellularhacker 💜🧪 retweeted
Me acaban de obligar a cerrar la computadora en un café en Madrid, recién me sentaba.
Argumentan querer favorecer la rotación de mesas. Me comprometo a irme en el tiempo que ellos quieran, me lo negaron e insólitamente agregan “Sin computadora quédate el tiempo que quieras”
Sigo sin entender que ganan
Cellularhacker 💜🧪 retweeted
#jisabakan 配置の都合上爆音の森だがご自宅に無理なく置けそうな機材😂
Se han cargado Workday, una plataforma SaaS utilizada por más de 11.500 organizaciones de todo el mundo, como Netflix, Acceture, Nasdq y muchas empresas y organismo muy grandes.
Estaban haciendo pruebas de la infraestructura de recuperación ante desastres (Disaster Recovery, DR), se han conectado por error a las bases de datos de producción y las han corrompido.
Han parado la plataforma mientra analizan los daños, pero podrían quedar incoherencias de los datos.
La caída afecta a empleados, responsables de recursos humanos, departamentos financieros y proveedores que usan Workday.
Consecuencias:
- Imposibilidad de fichar, consultar nóminas, solicitar vacaciones o gestionar beneficios.
- Bloqueo de contrataciones, altas, bajas y cambios contractuales.
- Interrupciones de procesos contables y administrativos.
- Problemas para presentar solicitudes o completar contrataciones.
- Fallos de API, sincronizaciones, integraciones y tareas programadas.
Esto es aun más grave que la caída de Microsoft para grandes empresas, sobre todo si la corrupción de datos no se puede arreglar.
Esto es lo que pasa cuando sustituyes profesionales formados por IA. Son fallos de aficionado, van a pagar caro el ahorro.
Los administradores de las empresas tecnológicas no están entendiendo nada, se han tragado las mentiras de Altman, Amodai y demás gurús de la IA, que sólo quieren más dinero para su burbuja.
Cellularhacker 💜🧪 retweeted
RAM prices are so high that Red Hat engineers are looking at SSDs to hold part of your virtual machines' memory.
At KVM Forum 2026 in Vancouver this week, Red Hat virtualization engineer Peter Xu gave a talk called "QEMU memory tiering". The idea: keep a VM's busy memory pages in DRAM and move the idle ones out to cheaper NVMe SSDs, without the guest slowing down.
"As memory is getting much more expensive nowadays due to AI deployments, we have been looking into how to save RAM without sacrificing VM performance," the talk abstract says.
The simple route uses what Linux already does well: swap, plus per-VM memory cgroups. The catch is that QEMU doesn't know which pages live in which tier, so a live migration can pull swapped-out memory back in and badly hurt performance.
Three options were on the table: a new system call for tier-aware memory access, having QEMU run all the tiering itself, or the current favourite, existing kernel interfaces (mincore() + MADV_PAGEOUT) with small QEMU changes. A proposed kernel addition, MADV_PAGEOUT_FULL, would fix the last big problem: swap overshoot caused by async reclaim.
Cellularhacker 💜🧪 retweeted
如果你恨一个人
你就去偷偷潜入他的服务器然后执行
chmod 666 /bin/chmod
如果过了几天你看到他重装系统了
你还可以嘲笑一波他根本不懂 linux
Cellularhacker 💜🧪 retweeted
🚨Cyber Alert ‼️
🇰🇷South Korea - 𝗦𝗮𝗺𝘀𝘂𝗻𝗴 𝗘𝗹𝗲𝗰𝘁𝗿𝗼𝗻𝗶𝗰𝘀
The n0n hacking group claims to have compromised sensitive data belonging to Samsung Electronics.
The allegedly stolen data includes US Smart TV viewing records, household-level geographic information, device advertising features, advertising model training data, advertising intelligence records through October 2026, and internal data governance documents.
Threat actor: n0n
Sector: Manufacturing
Data exposure (claimed): Not specified
Data type: Smart TV viewing records, household geographic information, advertising data and internal governance documents
Observed: Nov 15, 2026
Status: Pending verification
ESIX©: 5.39
Full details and impact assessment on HackRisk.io
Cellularhacker 💜🧪 retweeted
The Transportation Department earlier this year showed off just how old some of the FAA’s air traffic systems are and what they are working to upgrade. That includes *paper strips* still used to track flight routes in favor of electronic strips
发现一个特别好笑又扎心的事:现在的 AI Agent 跟职场新人一模一样——不记笔记的时候全凭本事干对,一旦开始自己写“错题本”,反而越干越废。
刚刚刷榜拿下 HuggingFace 24小时与7天双料第一的 KAIST 新论文(WikiTrace),干脆利落地扒下了 Agent 记忆系统的底裤:
那些三次裸考都能全对的简单任务,加上“历史经验”之后居然直接翻车了。团队拉出 355 个翻车现场一查,高达 52% 的弱智操作,全是因为 AI 死板照抄了自己以前留下的“半吊子经验”。
这就是离谱的“记忆致残(Memory-Induced Degradation)”。👇
Cellularhacker 💜🧪 retweeted
Replying to @TheBobPony
btw, if your devices somehow don't have ipv4 (aka basically having their ip conflicted one on others) you end up getting locked out or stuck on oobe
(yet microsoft didn't put his own ipv6, that's why)







































































