A selection of good papers from USENIX Security ’17
I have briefly talked about Adrienne’s and April’s talk at USENIX Security 2017, but I have not given much light to other papers and presentations that got my attention at the conference. I thought I should do a round up of good content for this conference, and if I can manage, go back to it later. First of all, the full proceedings are available on the Program page of the conference. As usual, US
What does #shellshock mean for Gentoo?
This is going to be interesting as Planet Gentoo is currently unavailable as I write this. I’ll try to send this out further so that people know about it. By now we have all been doing our best to update our laptops and servers to the new bash version so that we are safe from the big scare of the quarter, shellshock. I say laptop because the way the vulnerability can be exploited limits the impact
GLIBC 2.17: what’s going to be a trouble?
So LWN reports just today on the release of GLIBC 2.17 which solves a security issue and looks like was released mostly to support the new AArch64 architecture – i.e. arm64 – but the last entry in the reported news is possibly going to be a major headache and I’d better post already about it so that we have a reference for it. I’m referring to this: The `clock_*' suite of functions (declared in <t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Reverse engineering notes: USB sniffing
Powered by… Gentoo/FreeBSD
Gentoo Miniconf 2016
Debunking x32 myths
The end of an era, the end of the tinderbox
GSoC Proposal: a better log collector and analyzer
Gems make it a battle between the developer and the packager
A worldly opponent
Are -g options really safe?
Buildsystem quirks: now you know why you don’t rely on uname
Choosing an MD5 implementation
Cross-compilation and pkg-config
A shared library by any other name
Library SONAME bumps and .la files: some visual clues
About GLIBC 2.14, EGLIBC, and Gentoo
Gold readiness obstacle #1: Berkeley DB
Month: May 2011