mappu

76 ms·

841.
by mappu 9y ago
> that 4chan mascot https://en.wikipedia.org/wiki/Yotsuba%26 ! (SFW)
842.
As predicted, more branch prediction processor attacks are discovered(arstechnica.com)
11 points by mappu 9y ago|0 comments
843.
by mappu 9y ago
MVS requires import path compatibility. For semver-major changes the /v2/-style workaround is OK, except when a package is still v0. What happens in vgo if MY_APP depends on A and B, which both depend on different, incompatible v0
844.
by mappu 9y ago
The Go runtime for Lambda allows arbitrary binaries, with a CGI-like-but-incompatible interface.
845.
by mappu 9y ago
One of mingw{,-w64}'s major contributions is a gcc-compatible replacement set of headers and import libraries, instead of using the Windows SDK or MSVC versions. These work great most of the time, but if you start hooking deeply into w
846.
by mappu 9y ago
A generation ago, many (most?) apps were C++ for Win32. That means wndprocs, LPARAM, pointer casts everywhere. No STL, buggy templates. Dialog resources, manual layout of controls. Build the app for both * A and * W, ship unicows for win95
847.
by mappu 9y ago
No crashes on Debian harfbuzz.
848.
by mappu 9y ago
In that situation, the data is "inaccessible" but a data breach during the backup retention period will still leak their details. We can already achieve that result by removing records from the live DB and ignoring the whole backu
849.
by mappu 9y ago
Help me understand - that seems like it just centralizes the problem. Since the key is now PII-equivalent, how is the key storage backed up?
850.
by mappu 9y ago
It's not clear how to implement 'right to be forgotten' inside backed-up data, too.
851.
by mappu 9y ago
KIO does some similarly magical things e.g. click a URL to a jpg file, and it opens in your picture viewer app instead of the browser.
852.
by mappu 9y ago
HE-AAC has the colossal downside that there is no free software encoder. FFmpeg/libav don't do HE. FDK/libaacplus are non-free. neroAacEnc always used to have the best quality, but that's shareware.
853.
by mappu 9y ago
I think this launch was commercial - it put three satellites from two private companies (Planet Labs / Spire Global) into orbit.
854.
by mappu 9y ago
"10nm" and "7nm" are marketing terms that are not directly comparable across foundries.
855.
by mappu 9y ago
> > 2. The Go code generator usually produces highly unidiomatic Go. > using the generated structs as the main domain types in your code can be up-and-down At $DAYJOB we solve this by doing code generation outward from our doma
856.
by mappu 9y ago
Are those earlier-mentioned attacks against HyperThreading and caches still viable? If not, were they resolved in OpenSSL, in the OS, or in hardware?
857.
by mappu 9y ago
You're right. Thanks for clarifying.
858.
by mappu 9y ago
This is not specifically a vulnerability in TLS-SNI-01 - more like a major misconfiguration by the shared hosting provider, to share ACME secrets. I guess TLS-SNI-01 does share part of the blame for making this possible in the first place.
859.
by mappu 9y ago
>I'm not really sure how I can prove that the code I'm running is the code you'll find on GH though. I think this attestation is something Amazon (and other cloud providers) could offer in the future - they're the o
860.
by mappu 9y ago
>...but those CPUs are still speculative out-of-order super-scalars aren't they? Not universally, even in current-generation devices e.g. the Cortex A53 and A55 are in-order and were explicitly mentioned as safe by ARM. Snapdragon
861.
by mappu 9y ago
I use a binary distro and definitely don't want to be running massively slowed-down software mitigations on a corrected CPU. Although actually, we already are - binary distros already don't take into account per-microarchitecture
862.
by mappu 9y ago
Some ARM cores are genuinely implicated in this: https://news.ycombinator.com/item?id=16058454
863.
by mappu 9y ago
The patch was updated to v3: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-D... Compared to the x86 patches, these are still in the review stage, aiming to upstream for 4.16. I guess they'll find
864.
KAISER / PTI issue may also affect ARM CPUs(lwn.net)
8 points by mappu 9y ago|2 comments
865.
by mappu 9y ago
Exactly. The inadvertent aliasing can produce situations like this: https://play.golang.org/p/XUtyQ6ShYaz , or more plausibly: https://play.golang.org/p/Xx8lZWVWgIu
866.
by mappu 9y ago
Sure, i meant that x and y are different identifiers.
867.
by mappu 9y ago
My Go gotcha: x = append(y, ...) is usually unsafe for x != y. I want to find/build a linter that catches such cases...
868.
by mappu 9y ago
Apple's bug bounty program does not cover macOS.
869.
by mappu 9y ago
Responsible disclosure would have been to product-security@apple.com. Do apple have a bug-bounty program?
870.
by mappu 9y ago
On my device it shows as "( t )": https://i.imgur.com/b3Yhh1I.png I'm not sure why.

More ›