Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker) profile picture
๋Œ€ํ•œ๋ฏผ๊ตญ ๋™์ž‘๊ตฌ
Joined August 2022
Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)Photo by Cellularhacker ๐Ÿ’œ๐Ÿงช (@cellularhacker)
16ํ•™๋ฒˆ ์ž…๋‹ˆ๋‹ค. ํ™”๋ชฉํ•˜๊ฒŒ ์ง€๋‚ด๋ ค๊ณ  ์ฐธ๊ณ  ๋˜ ์ฐธ๊ณ  ๊ทธ๋ƒฅ ๋„˜์–ด๊ฐ”๋˜๊ฒƒ๋“ค, ์ด์ œ๋ถ€ํ„ฐ๋Š” ์นผ๊ฐ™์ด ์ณ๋‚ด๊ฒ ์Šต๋‹ˆ๋‹ค. - ํ‹ฐ๋Œ ๋งŒํผ ์ด๋ผ๋„ ๊ตญ๋ฏผ์˜ํž˜์— ๋™์กฐํ•˜๋Š” ์‚ฌ๋žŒ - ์ขŒ๋นจ์ด ์–ด์ฉŒ๊ณ  ํ•˜๋Š” ์‚ฌ๋žŒ - ๊ทธ๋ž˜๋„ ์ด์žฌ๋ช…์ด ... ์–ด์ฉŒ๊ตฌ ํ•˜๋ฉด์„œ ๋‚ด๋ž€๋™์กฐ ์ง์Šน๋“คํ•œํ…Œ ํ‹ฐ๋Œ์ด๋ผ๋„ ํŽธ ๋“œ๋Š” ์‚ฌ๋žŒ (์ด์–ด์ง)
1
2
315
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
ํšŒ์‚ฌ์—์„œ๋„ ๊ทธ๋ ‡๊ณ  AI๊ฐ€ ๋‚˜ํƒ€๋‚˜๊ณ  ๋‚˜์„œ ์˜คํžˆ๋ ค ์ธ๊ฐ„์ด ํ•  ์ผ์ด ์—„์ฒญ๋‚˜๊ฒŒ ๋งŽ์•„์ง„ ๋А๋‚Œ... ์š”์ฆ˜ ์—…๋ฌด๋Ÿ‰์€ ๊ณผ๊ฑฐ๋ž‘ ๋น„๊ต๋„ ๋ชปํ•œ๋‹ค...
์ง€๊ธˆ ์„ธ๋ฌด์‚ฌ AI ์‹œํ—˜ ์‚ฌํƒœ๋กœ ๋ฒŒ๋ฒŒ ๋–จ๊ณ  ์žˆ๋Š” ๊ธฐ๊ด€ ์ด์ƒˆ๋ผ๋“ค ใ…‹ใ…‹ใ…‹ใ…‹ใ…‹ ์กด์žฌ์ด์œ ๊ฐ€ ๋ญ๋ƒ
1
133
12
311
22,665
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
๊ทธ๋Ÿฌ๋‹ˆ๊นŒ... ์ด๋ฆ„๋งŒ ๋“ค์œผ๋ฉด ์•„๋Š” ๋น…ํ…Œํฌ๊ฐ€ ๋ฉ”์ด์ € ๋ชจ๋ธ๋„ ์•„๋‹ˆ๊ณ  ์ž์ฒดํ›ˆ๋ จ์ธ์ง€ ์–ด๋””์„œ ๊ฐ€์ ธ์™”๋Š”์ง€ ๋ชจ๋ฅผ ๊ตฌ๋ฆฐ AI ๋“ค๊ณ ์™€์„œ ๊ทธ๊ฒƒ๋„ ํŒŒ์ผ๋Ÿฟ ํ”„๋กœ์ ํŠธ๋„ ์•„๋‹Œ ์ค‘์š”๋„ ๋†’์€ ์‹ค์ œ ์šด์˜ ์‹œ์Šคํ…œ์—๋‹ค๊ฐ€ ์•ž์œผ๋กœ AI๋กœ ์ž‘์—…ํ•ด์„œ ์ธ๊ฑด๋น„๋ฅผ ์ค„์ด๋ผ๊ณ  ํ•˜๋ฉด์„œ ๋ฐ˜์˜ํ•  ๋•Œ ๊ฒ€ํ† ๋„ ํ•˜์ง€ ๋ง๋ผ ์ง€์‹œ๋Œ€๋กœ ์ž‘์—…ํ•˜๋‹ค๊ฐ€ ๊ฒฐ๊ตญ ์„œ๋น„์Šค๊ฐ€ ํ„ฐ์กŒ๋‹ค๋Š”๊ฑด๊ฐ€....? ์Œ... ๊ทธ๋ ‡๊ตฐ
9
29
4
144
25,097
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
์ œ๊ฐ€ Daum์—์„œ ์˜คํ”ˆํ•œ API ์„œ๋น„์Šค ์ค‘, ๊ฐ€์žฅ ์ž๋ž‘์Šค๋Ÿฌ์šด ๊ฒƒ ์ค‘ ํ•˜๋‚˜๊ฐ€ '๊ฐœ๋ฐœ์ž๋ฅผ ์œ„ํ•œ ์šฐํŽธ๋ฒˆํ˜ธ ์กฐํšŒ ์„œ๋น„์Šค'์˜€๋Š”๋ฐ์š”. ์ด์ œ 12๋…„์ด ํ˜๋Ÿฌ์„œ, ๋ผ์ด๋ธŒ๋Ÿฌ๋ฆฌ ํ˜ธ์ŠคํŒ… ๋„๋ฉ”์ธ์„ ๊ต์ฒดํ•ด์•ผ ํ•˜๋‚˜ ๋ณด๋„ค์š”. Daum๊ณผ Kakao ๋„๋ฉ”์ธ ๋ถ„๋ฆฌ ๋•Œ๋ฌธ์ธ๊ฒƒ ๊ฐ™์Šต๋‹ˆ๋‹ค. ์˜ค๋žœ ๊ธฐ๊ฐ„ ํ•˜์œ„ํ˜ธํ™˜์„ฑ์„ ์œ ์ง€ํ•ด์™”์ง€๋งŒ, ๊ฐœ๋ฐœ ์œ ์ง€ ๋ณด์ˆ˜๊ฐ€ ์•ˆ๋˜๋Š” ์‚ฌ์ดํŠธ๋ฅผ ์œ„ํ•ด์„œ, ์•„์˜ˆ ์ผ๋ฐ˜ ์‚ฌ์šฉ์ž์—๊ฒŒ ๊ณต์ง€๋ฅผ ํ•ด์•ผ ํ•˜๋‚˜ ๋ด…๋‹ˆ๋‹ค. ์ด ๊ณต์ง€๊ฐ€ ๋ณด์ด๋Š” ์›น ์‚ฌ์ดํŠธ๋Š” 11์›”๋ง๊นŒ์ง€ ์ˆ˜์ •ํ•˜์‹œ๊ธฐ ๋ฐ”๋ž๋‹ˆ๋‹ค. ๐Ÿคฃ ๊ตฌ. Daum ์šฐํŽธ๋ฒˆํ˜ธ ์กฐํšŒ ์„œ๋น„์Šค๊ฐ€ ์ œ๊ณต ๋˜๊ธฐ ์ „๊นŒ์ง€๋Š”, ๊ฐœ๋ณ„ ์›น ์‚ฌ์ดํŠธ ํšŒ์› ๊ฐ€์ž… ์‹œ, ์šฐํŽธ ๋ฒˆํ˜ธ ๊ฒ€์ƒ‰ ๊ธฐ๋Šฅ์€ ๊ตฌํ˜„๋„ ์œ ์ง€๋ณด์ˆ˜๋„ ๋งŒ๋งŒ์น˜ ์•Š์•˜์Šต๋‹ˆ๋‹ค. ๋งค๋ฒˆ ์—…๋ฐ์ดํŠธ ๋˜๋Š” ์šฐํŽธ ๋ฒˆํ˜ธ, ์ƒˆ๋กœ ์ถ”๊ฐ€๋˜๋Š” ์ฃผ์†Œ, ์ง€๋ฒˆ ์ฃผ์†Œ์™€ ๋„๋กœ๋ช… ์ฃผ์†Œ ๋“ฑ๋“ฑ... ๊ทธ๋™์•ˆ ๊ฐœ๋ฐœ์ž๋“ค์˜ ์ˆ˜๊ณ ๋ฅผ ๋งŽ์ด ๋œ์–ด์ฃผ์—ˆ์„ ๋ฟ๋งŒ ์•„๋‹ˆ๋ผ ๊ตญ๋ฏผ ํŽธ์ต์— ์ƒ๋‹นํžˆ ์˜ํ–ฅ์„ ์ฃผ์—ˆ์Šต๋‹ˆ๋‹ค. ์•ž์œผ๋กœ๋„ ์ค‘๋‹จ๋˜์ง€ ์•Š๊ณ  ๊ณ„์†ํ•ด์„œ ์„œ๋น„์Šค๋ฅผ ์ œ๊ณตํ•ด ์ฃผ์—ˆ์œผ๋ฉด ํ•˜๋Š” ๋ฐ”๋žจ์ด๋„ค์š”.
6
273
23
463
39,408
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
์šฐ๋ฆฌ ์ดํ˜์ค‘ CISO๋‹˜์ด ์ด๋ฒˆ์—๋„ ์•„์ฃผ ์ข‹์€ ๊ธ€์„ ์˜ฌ๋ ค์ฃผ์…จ๋„ค์š”. ์ฒจ์–ธํ•˜๋ฉด, 2006๋…„ ์ดˆ๊ธฐ ๋ง๋ถ„๋ฆฌ ๋„์ž…์‹œ ์„ ์ง„๊ตญ์‹์˜ '๋ฐ์ดํ„ฐ ์ค‘์š”๋„ ๊ธฐ๋ฐ˜ ๋ง๋ถ„๋ฆฌ(์ง€๊ธˆ์˜ N2SF)'๋ฅผ ๋„์ž…ํ–ˆ์—ˆ๋”๋ผ๋ฉด ์–ด๋• ์„๊นŒ ํ•˜๋Š” ์ƒ๊ฐ๋„ ๋“ญ๋‹ˆ๋‹ค. ๋‹น์‹œ ์ผ์„ ์—์„œ ๋ฐ์ดํ„ฐ๋ถ„๋ฅ˜๋ฅผ ์ž˜๋ชปํ• ์ˆ˜ ์žˆ๋‹ค๋Š” ๋ถˆ์•ˆ๊ฐ, ๊ฐ„๊ธ‰ํžˆ ๋Œ€์ฑ…์„ ์„ธ์›Œ์•ผ ํ•œ๋‹ค๋Š” ๋‹ค๊ธ‰ํ•จ ๋“ฑ์ด 'ํš์ผ์  ๋ง๋ถ„๋ฆฌ'๋ฅผ ๋“ฑ์žฅ์‹œ์ผฐ๊ณ , ๊ทธ๊ฒƒ์ด ๊ฒฐ๊ตญ์—๋Š” SaaS ํ™œ์šฉ, ํด๋ผ์šฐ๋“œ ๊ธฐ๋ฐ˜ ๋ณด์•ˆ๊ด€์ œ ๋“ฑ ๋ณด์•ˆ์˜ ๊ณ ๋„ํ™”๋ฅผ ๋„ˆ๋ฌด๋‚˜๋„ ์˜ค๋žซ๋™์•ˆ ๋ง‰๊ณ  ์žˆ์—ˆ๋˜.... ๊ทธ ๋Œ“๊ฐ€๋ฅผ ์šฐ๋ฆฐ ์ง€๊ธˆ ์น˜๋ฃจ๊ณ  ์žˆ๊ตฌ์š”. [์ดํ˜์ค‘ CISO ์นผ๋Ÿผ] ๋ง๋ถ„๋ฆฌ ์ดํ›„์˜ ๋ง๋ถ„๋ฆฌ: AI ์‹œ๋Œ€ ๊ธˆ์œต๋ณด์•ˆ์˜ ๋‹ค์Œ ์งˆ๋ฌธ dailysecu.com/news/articleViโ€ฆ
3
14
38
1,986
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
Block bots in 10 lines of code. No captchas, no friction for real customers. Sign up for free.

49
77
4
643
13,008,261
20ๆžšใ‚‚ใ„ใ‘ใ‚‹ใ‚“ใงใ™ใ‹โ€ฆ๏ผ
20
1,074
2
11,909
100,783
ๅคไผ‘ใฟใฎ็ตตๆ—ฅ่จ˜ใงใ™ใ€‚ #ใƒ›ใƒญใ‚ใกใ‚ƒๅญฆๅœ’็ฅญ_DAY2
215
998
40
9,003
191,150
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.
395
3,209
185
19,376
858,085
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.
FFMPEG was right all along and people gave them too much shit for it
131
760
51
7,601
368,882
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
968
110
102
4,774
924,318
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
์•„ ๋„˜ ์›ƒ๋„ค ์–ด์ œ ๋ฏธ๊ตญ ๊ณตํ•ญ ์ฃ„๋‹ค ๊ทธ๋ผ์šด๋“œ์Šคํƒ‘ ๋์„ ๋•Œ ๋น„ํ–‰๊ธฐ ํƒ€๊ณ  ์žˆ๋˜ ํ›„๋ฐ”์Šคํƒฑํฌ ๋ณด์ปฌ์ด ์ฆ‰ํฅ ์ฝ˜์„œํŠธ ํ–ˆ๋‹ค๊ณ  ใ…‹ใ…‹ใ…‹ใ…‹ใ…‹ใ…‹ใ…‹ใ…‹
Looks like some stuck travelers got a concert from the singer of Hoobastank during the national air traffic shut down
742
28
871
62,780
#jisabakan ้…็ฝฎใฎ้ƒฝๅˆไธŠ็ˆ†้Ÿณใฎๆฃฎใ ใŒใ”่‡ชๅฎ…ใซ็„ก็†ใชใ็ฝฎใ‘ใใ†ใชๆฉŸๆ๐Ÿ˜‚
2
15
231
14,559
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
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.
77
275
38
1,453
96,679
์ œ๋ฐœ ๋ถ€ํƒ์ธ๋ฐ ์ง€์ž์ฒด์—์„œ ํ•ด์•ผํ•  ์ผ๊นŒ์ง€ ํ˜‘๋ ฅ์‚ฌ์— ๋– ๋„˜๊ธฐ๋Š” ์ผ์ด ์—†๋„๋ก ์ฑ™๊ฒจ๋ด์ฃผ์‹ค ์ˆ˜ ์žˆ์œผ์‹ค๊นŒ์š”? - 01) ๊ฐ€๋งŒํžˆ ์žˆ๋‹ค๊ฐ€ - 02) ๊ฐ‘์ž๊ธฐ - 03) ๋ชจ๋“  ๊ธฐ๊ด€์—์„œ ๋˜‘๊ฐ™์€ ๋‚ด์šฉ์„ - 04) ๋ถˆํ•„์š”ํ•œ ํ–‰์ •๋ฌธ์„œ ์–‘์‹์œผ๋กœ - 05) ์ˆ˜๊ธฐ๋กœ ์ œ์ถœํ•  ๊ฒƒ์„ ์š”์ฒญํ•˜๋Š”๋ฐ (๊ณ„์†)
๋„ค, ์˜ณ์€ ๊ฒฐ์ •์„ ํ•˜์…จ์Šต๋‹ˆ๋‹ค. ์•ˆ๋ณด์‹ค 3์ฐจ์žฅ๋‹˜๊ป˜์„œ ์ฒ˜์Œ ๋ถ€์ž„ํ•˜์‹ค ๋•Œ๋ถ€ํ„ฐ ๊ด€์‹ฌ์„ ๋ณด์ด์‹œ๋”๋‹ˆ ๋“œ๋””์–ด ๊ณต์‹ ๋ฐœํ‘œ ๋˜์—ˆ๋„ค์š”. ์—ญ์‹œ ๊ธฐ๋ณธ์ด ์ค‘์š”ํ•ฉ๋‹ˆ๋‹ค. ์ž์นซ ๊ฒ‰๋ณด๊ธฐ์—๋งŒ ๊ทธ๋Ÿด์‹ธํ•œ ๋Œ€์ฑ…์„ ๋‚ด๋†“์•˜๋‹ค๋ฉด, ์•ž์œผ๋กœ ๋” ํฐ ํ™”๋ฅผ ๋ถˆ๋Ÿฌ์™”์„ ๊ฒƒ์ž…๋‹ˆ๋‹ค. ์ž˜ํ•˜์…จ์Šต๋‹ˆ๋‹ค! ํ•ดํ‚น ๊ธ‰์ฆํ•˜์žโ€ฆ้‘, ๋ฏผยท๊ด€ยท๊ตฐ IT ์ž์‚ฐ ์ „์ˆ˜ ์ ๊ฒ€ naver.me/x8kZMYgB
1
6
1
4
664
์•„๋งˆ ์ฐพ์•„๋ณด์‹ค ์ˆ˜ ์žˆ๋Š” ์œ„์น˜์— ์žˆ์œผ์‹œ๋‹ˆ๊นŒ, ๋…ธ๋ ฅ์„ ํ•˜์‹œ๋ฉด ํŠน์ •ํ•˜์‹ค ์ˆ˜ ์žˆ๋Š” ์ •๋ณด์ง€๋งŒ - 09) ๋ฌด์Šจ CVE๊ด€๋ฆฌ๋ฅผ - 09-1) ์—‘์…€ ์‹œํŠธ ๋‚ด์—์„œ๋„ - 09-2) ์‚ฌ์ดํŠธ ํ•˜๋‚˜๋‹น ํ•˜๋‚˜์˜ ํ–‰์— - 09-3) ํฌํŠธ๋ฅผ TCP/UDP ์ค‘์— ํ•˜๋‚˜๋งŒ ์ ์œผ๋ผ๋Š” ์‹์œผ๋กœ ๋งŒ๋“ค์–ด์„œ (๊ณ„์†)
1
2
3
144
- 09-4) ์—ด๋ ค์žˆ์œผ๋ฉด ๋ฌด์กฐ๊ฑด CVE ๋„ฃ์–ด์„œ ์กฐ์น˜์˜ˆ์ • ๋ฐ ์กฐ์น˜๋ฐฉ๋ฒ•์„ ๋„ฃ๊ฒŒ๋”๋งŒ ๋˜์–ด์žˆ๋Š”์ง€... - 10) ๋˜, ์„œ๋ฒ„๋ณด์•ˆํŒจ์น˜๋ฅผ ํ•˜๋ ค๋ฉด ๋ฏธ๋Ÿฌ์„œ๋ฒ„์— ์ ‘์†์ด ๋˜์–ด์•ผ ํ•˜๋Š”๋ฐ, ๊ทธ๊ฑธ ๋ง‰์•„๋†“๊ณ ์„  ๋ณด์•ˆ์„ ๊ธฐ๋Œ€ํ•˜๋Š”๊ฒŒ ๋„ˆ๋ฌด ๋‹น์—ฐํ•œ๊ฒŒ ๊ด€๊ณต์„œ ์ „์‚ฐ์‹ค ์ž…๋‹ˆ๋‹ค...
1
1
104
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.
18
88
12
628
32,617
Cellularhacker ๐Ÿ’œ๐Ÿงช retweeted
ๅฆ‚ๆžœไฝ ๆจไธ€ไธชไบบ ไฝ ๅฐฑๅŽปๅทๅทๆฝœๅ…ฅไป–็š„ๆœๅŠกๅ™จ็„ถๅŽๆ‰ง่กŒ chmod 666 /bin/chmod ๅฆ‚ๆžœ่ฟ‡ไบ†ๅ‡ ๅคฉไฝ ็œ‹ๅˆฐไป–้‡่ฃ…็ณป็ปŸไบ† ไฝ ่ฟ˜ๅฏไปฅๅ˜ฒ็ฌ‘ไธ€ๆณขไป–ๆ นๆœฌไธๆ‡‚ linux
130
80
22
2,786
270,255
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
9
200
24
418
38,015