Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!



Errata Prompts Intel To Disable TSX In Haswell, Early Broadwell CPUs

johndoe42 Re:So how does one find out /apply "fix" with linu (131 comments)

If you have a recent version of the cpuid tool, you can run:

cpuid |grep RTM

and you'll see something like:

RTM: restricted transactional memory = false
RTM: restricted transactional memory = false
RTM: restricted transactional memory = false
RTM: restricted transactional memory = false

/proc/cpuinfo doesn't show it, presumably because no kernel support is needed at all for this feature. (And that's why, if this is indeed a privilege escalation issue, it won't be easily fixed with a kernel change.)

about a week ago

Errata Prompts Intel To Disable TSX In Haswell, Early Broadwell CPUs

johndoe42 Re:Problem and possible alternatives (131 comments)

Regarding the alternatives, Intel cannot simply remove these instructions opcodes because previous code would fail. I assume that the patch will make all hardware transactions fail on startup, with an specific error (EAX bit 1 indicates if the transaction can succeed on a retry; setting this flag to 0 should trigger a software transaction). In such case, execution continues at the fallback routine indicated in the XBEGIN instruction, which should begin a software transaction. Effectively, this will be similar to a software TM (STM) with additional overheads (starting the hardware transaction and aborting it; detecting conflicts with nonexistent hardware transactions) that would make it slower than a pure STM implementation.

This seems unlikely to me. I'd expect that the patch will clear the cpuid bit for TSX and cause #UD (undefined opcode) on XBEGIN, etc.

about a week ago

Ask Slashdot: Life Beyond the WRT54G Series?

johndoe42 Re:Netgear R7000 (426 comments)

Buying an R7000 is a waste of money. The whole "AC1900" class is a joke -- they squeeze out the extra Mbps by supporting a nonstandard, Broadcom-only modulation in the 2.4 GHz band. Good luck finding any client devices that can use that modulation.

Stick with AC1750 and stop feeding the marketing trolls.

about two weeks ago

Ask Slashdot: Life Beyond the WRT54G Series?

johndoe42 Re:Atheros and OpenWRT (426 comments)

The TP-Link Archer C7 v2 is pretty mature. The v1 is discontinued, and most US-based vendors are now explicitly advertising v2 hardware. The only real caveat is that the open-source ath10k support is very slightly flaky -- you may have intermittent issues if you have a Macbook Pro. This will probabaly be fixed soon.

about two weeks ago

Engineers Invent Acoustic Equivalent of One-Way Glass

johndoe42 Re:Except for the fact that... (114 comments)

This is incorrect. You can't build a passive device that is 100% transmissive from one side and 100% reflective on the other side.

You can, however (in theory), build a device that with these properties:

  1. Light from side A is transmitted and comes out side B
  2. Light from side B is absorbed and turns into heat
  3. Absorbed heat is re-radiated, mostly from side A

This thing will be non-reciprocal. I've never heard of anyone building one that looks like a sheet of glass, but they're common for microwaves -- they're called circulators. There's a reason that this new contraption is called an acoustic circulator. The only misleading part is that one-way glass is reciprocal -- this new thing is much more impressive than one-way glass.

about 7 months ago

Reuters: RSA Weakened Encryption For $10M From NSA

johndoe42 Re:RSA sold you out (464 comments)

Here is what I personally don't get and since I'm not a crypto guy maybe I'm missing something but here looks like all these attacks come from using a RNG that has been rigged to be less than random, but why use their RNG when there are so many sources of randomness in the world?

There is the background radiation of the universe for starters, and how many webcams are freely accessible in heavily trafficked public places? It shouldn't be hard to write a program that does a quick head count, multiple that by the dollar amount of the biggest box office draw last week. How many letters is in headlines of the top 60 newspapers on the planet? Multiple that by the amount of temp detected by 30 weather stations and divide by the number of folks who went to see the fourth most popular movie yesterday squared by the ratings of the most popular reality show.

You can do things like this (with a little bit more care) to generate numbers that can't be predicted in advance. Unfortunately, that's not the point. Web servers need random numbers that can't be guessed or manipulated by anyone, and they need to generate lots of them. If everyone generated the same random numbers (because they looked at the same webcams), then those numbers aren't useful for cryptography.

about 7 months ago

Reuters: RSA Weakened Encryption For $10M From NSA

johndoe42 Re:Catastrophic (464 comments)

Except that RSA destroyed their whole business a couple of years ago when it was found that they'd left the root keys for their SecureID tokens on an unsecured, network-connected machine. After that no one could trust them again.

RSA lost my trust when I found out that root keys or critical secrets for the SecureID system existed in the first place.

If they designed the system well, they would make physical tokens and deliver the tokens and the keys for those tokens to the clients. They would not keep any record whatsoever of those keys, nor would they have a way to reconstruct them

As a physical analogy, a locksmith making safety deposit box keys should make a random key and not write down the key code

about 7 months ago

Tesla Model S Battery Drain Issue Fixed

johndoe42 That's a lot of 12V loss (239 comments)

Before the battery replacement, the car lost 3.5kWh/day. After the replacement, it lost 1.1kWh/day. That's a difference of 2.4kWh/day, which is 100W. That's something like 8 Amps internally leaking in the 12V battery. That seems shockingly high. Or maybe there's something else going on. If the battery was marginal, then perhaps the car's DC-DC converter was continually "charging" it but actually overcharging it. Then it would be electrolyzing 8A worth of water and battery acid. I expect that would make a giant mess. Alternatively, it just keeps running the DC-DC converter at very low output. The DC-DC converter could be incredibly inefficient when producing just a little bit of current (Tesla is reputed to use a huge (~200A) DC-DC converter, so the thing could be running at about 1% of rated output at, say, 10% efficiency).

about 8 months ago

Bitcoin Miners Bundled With PUPs In Legitimate Applications Backed By EULA

johndoe42 Re:Incorrect (194 comments)

Or we could finally fix the law and declare EULAs to be unenforceable. Unilateral contracts like EULAs are out of control.

about 9 months ago

D-Link Router Backdoor Vulnerability Allows Full Access To Settings

johndoe42 Re:Will this stupidity ever end? (228 comments)

A class action lawsuit for gross negligence might do the trick.

Sometimes I think that things like this should be felonies, though. Criminal offense or not, in a sensible world this would put alphanetworks out of business.

about 10 months ago

Using Java In Low Latency Environments

johndoe42 Re:Warm up is a big deal (371 comments)

These people should be using a real time Java VM and an ahead of time compiler for those parts.

It means you can skip the warm up. The only problem with it is you can't hire regular Java guys - real time Java is a little bit special, and you can't use regular Java collections and other things in the ways you'd expect.

That's not the only problem. Doing this switches you from using a well-standardized, well-supported language to a nonstandard subset. This removes a lot of the advantages of Java.

One of the most technically competent exchanges I work with is trying out Azul, which is (AFAIK) the top-of-the-line low-latency JVM. I was a bit surprised to learn that their software didn't Just Work. In fact, it didn't work at all. So now they have to decide which AOT-compiling JVM to run and figure out how to support it. I suppose that Excelsior and gcj (eek!) would be other options.

My main point here is that, when low latency is involved, a lot of people cite the existence of high-quality real-time JVMs as evidence that Java is a good choice. These JVMs exist, but they are by no means panaceas, and users of Java for real-time or low-latency work will need to make a real technical and monetary investment in dealing with them. Hotspot is not (yet?) appropriate for this kind of thing. Oddly, .NET seems be in better shape here, at least in terms of AOT compilation.

1 year,18 days

Using Java In Low Latency Environments

johndoe42 Warm up is a big deal (371 comments)

I'm not a Java user, so I've never directly tuned for things like GC, nor do I interact with it directly. Warm up is a different story.

I interact with quite a few exchanges (over all kinds of protocols). Most are, unsurprisingly, written in Java. Almost all of them perform terribly at the beginning of the week. The issue is a standard one: the JVM hasn't JITted important code paths, and it won't until several thousand requests come in. For a standard throughput-oriented program, this doesn't matter -- the total time wasted running interpreted code is small. For a low-latency network service, it's a different story entirely: all of this wasted time happens exactly when it matters.

The standard fix seems to be to write apps to exercise their own critical paths at startup. This is *hard* when dealing with front-end code on the edge of the system you control. Even when it's easy, it's still something you have to do in Java that is entirely irrelevant in compiled languages.

If JVMs some day allow you to export a profile of what code is hot and re-import it at startup, this problem may be solved. Until then, low-latency programmers should weigh the faster development time of Java with the time spent trying to solve annoying problems like warm-up.

1 year,18 days

Physicists Discover a Way Around Heisenberg's Uncertainty Principle

johndoe42 Re:Does this break Quantum Key Distribution? (153 comments)

No, because the summary is (as usual) thoroughly overstated. This experiment, like any other form of quantum state tomography lets you take a lot of identical quantum systems and characterize them. For it to work, you need a source of identical quantum states.

As a really simple example, take a polarized light source and a polarizer (e.g. a good pair of sunglasses). Rotate the polarizer and you can easily figure out which way the light is polarized. This is neither surprising nor a big deal -- there are lots of identically polarized photons, so the usual uncertainty constraints don't apply.

The whole point of QKD (the BB84 and similar protocols) is that you send exactly one photon with the relevant state. One copy = no tomography.

about a year and a half ago

Magnetic Transistor Could Cut Power Consumption and Make Chips Reprogrammable

johndoe42 CMOS (126 comments)

First, keeping the voltage on requires power, which drives up the energy consumption of the microchip.

Barely. Almost every digital chip out there uses CMOS logic. The whole point of CMOS logic is that, when the gates aren't switching, no current flows. That means that no power is drawn. In practice, a little bit of current leaks, but this is a small effect at all but the smallest process sizes.

It's not all clear from the abstract how the authors expect to maintain a magnetic field without any static power consumption. Perhaps using ferromagnets, but I wouldn't hold my breath -- MRAM still hasn't happened.

about a year and a half ago

New Trusted HW Standard For Windows 8 To Support Chinese Crypto

johndoe42 The TPM has non-DRM uses (87 comments)

If you ignore all the weird DRM-ish uses (which are basically unsupported for now anyway [1]), the TPM makes a nice cryptographic token. Unfortunately, TPM v1.1 hard-coded the OAEP label to "TPM", which made it incompatible with everything. TPM v2.0 fixes this -- the label is now user-specified. That means that you can use it for modern hardware crypto (sadly, using SHA-1, which should be phased out).

[1] For meaningful DRM, you need an endorsed TPM, which most vendors don't provide. See

about 2 years ago

Increasing Wireless Network Speed By 1000% By Replacing Packets With Algebra

johndoe42 Interactions with 802.11n? (357 comments)

I don't think this is a good fit for 802.11n. From the paper:

We assume that there is are [sic] random erasures within in the network.

802.11n aggregates frames. This means that (at least for throughput-limited flows) multiple packets will be transmitted at once, and they're likely to all be lost together. This won't help. In any case, it makes sense for inherently lossy links to do their own FEC -- the end-to-end principle is not a good way to maximize capacity. But hacking around TCP like this seems silly -- just fix the problem at the link layer.

about 2 years ago

Material Breaks Record For Turning Heat Into Electricity

johndoe42 Efficiency in sensible units (102 comments)

TFA does a good job of using units that are incomprehensible to anyone who isn't an expert in thermoelectrics. But we can convert them...

Considering a thermoelectric device with a cold-side temperature of 350K and a hot-side temperature of 950K, respective waste-heat conversion efficiencies of ~16.5% and ~20% are predicted.

For a hot-side temperature of 950 K and a cold-side temperature of 350 K, the Carnot efficiency (i.e. the maximum possible efficiency of any device) is ~63%. So this is somewhere between 1/4 and 1/3 as efficient as it could possibly be. Large generators, such as combined cycle gas turbines are considerably more efficient, but these devices are small and silent. In other words: not bad.

about 2 years ago

Android Jelly Bean Much Harder To Hack

johndoe42 This doesn't affect the most important issues (184 comments)

It seems like the big vulneraibilites in mobile platforms these days involve apps doing things they shouldn't. Android is, for the most part, way ahead of Apple in terms of technical mitigations. Android sandboxes apps with explicit permission grants. Apple just vets them, incompletely. iOS also seems vulnerable to odd things, like this. Apparently executing unsigned code on iOS, if you can pull it off, sidesteps part of the sandbox. Android is based on the assumption that any app can execute unsigned code and it still tries to be secure.

more than 2 years ago

Move Over, Quantum Cryptography: Classical Physics Can Be Unbreakable Too

johndoe42 Re:Ridiculous, quantitatively. (126 comments)

I think it's a bit ridiculous, but not for these reasons.

(1) They suggest using very high temperatures, presumably to avoid exactly this issue.
(2) Not sure what you mean. She subtracts what from what? But see below.
(3) The authors propose adding low-pass filters for exactly this reason. They'll filter out high-frequency signals, leaving low-frequency components that have no effective time delay.

My attack would be for Eve to add a small probe signal -- she would insert a voltage source in the line, with a time-dependent (or even constant) voltage of her choice. She would then measure the correlation between the voltage she injects and the current in the wire. Alice and Bob are supposed to check for this by comparing the conditions on their ends of the wire with their expectation, but this assumes that they have measuring devices as good as Eve's.

The idea that the security is based on the second law of thermodynamics is, IMO, absurd. The second law says that a bunch of things that would decrease entropy are impossible. But Eve can do whatever she wants as long as she sinks enough entropy somewhere else -- Alice + Bob + the wire is not a closed system.

more than 2 years ago



IRS: give us machine-readable tax formulas

johndoe42 johndoe42 writes  |  about 4 months ago

johndoe42 (179131) writes "Now that tax day is almost over, it's time to ask the IRS to make it less painful. All of the commercial tax software is awful, overpriced, and incompatible with everything else. Some people have tried to do better: OpenTaxSolver and a rather large Excel spreadsheet are tedious manual translations of the IRS's forms. I'm sure that many programmers would try to make much friendlier tax software if they didn't have to deal with translating all of the IRS instructions. Let's petition the IRS to publish computerized formulas so that this can happen."


johndoe42 has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>