javanix

What regulations / standards would actually stop these things from getting out though?

ZFS.

I created a raid-Z zpool in 2010 on FreeBSD and those same bits, with two different drives, are still floating around intact 6 years later, across multiple different operating systems.

I'll be very curious to the the source of this native-Windows port.

Absurdly high taxes (my parents pay half my tax on a non-rural property twice as big about 120 miles north of me), but still, owning a home is hardly a fiscally ruinous proposition around here.

My property taxes this year were ~$4200 on an average sized lot and home, or roughly $350/month.

My last apartment cost $1050/month for a small two bedroom condo rental.

Well, in some areas, but it really depends on the market - the property taxes on my home in a University city of 200,000 are 1/3 of what I was paying in rent - with the interest on my mortgage the amount of "lost" money comes out to roughly the same amount for now.

As long as property taxes do not outstrip my interest rate, that ratio should stay in my favor going forward.

The /proc/kallsyms values are identical across identical kernel compilations.

Suppose you have a vulnerable CentOS 7 system that you want to exploit - you could get the proper addresses from your own CentOS 7 VM running the same kernel, apply those to a modified exploit compilation, and run that compilation on your target host.

Is SMAP required for mitigation, or is SMEP enough?

IIUC SMEP is on Sandy Bridge processors too.

Thanks, that worked.

How do you find those addresses?

I cannot for the life of me make it through a game of chess without making some catastrophic blunder.

If programming was that unforgiving I'd have to buy a new system every time I wrote a function.

I'd consider myself a good programmer but an absolutely terrible chess player, so no, I don't think they really have much bearing.

I wonder if the fish actually ended up helping with the mosquito population?