564300+ entries in 0.363s

decimation: yeah
the bell labs guy said
that
they charge him $500k per year per seat
decimation: but doesn't give
them a single step
toward 'making
their own'
decimation: asciilifeform: what it means is
that
they can enrich
themselves privately by stamping out copies and selling shit on ebay
decimation: yeah
the bell labs guy has issues hiring because very few schools are willing
to pay
the bezzlars required
to actually experiment with high-end process
decimation: asciilifeform: yeah and
there are some esoteric
telco applications
too
decimation: as I recall,
the guy claimed
that most of
the high-end fabs use cadence
tools
assbot: An Interview with Shahriar from
The Signal Path - Quisquous Quivering Quadripole |
The Amp Hour Electronics Podcast ... (
http://bit.ly/1A78JTP )
decimation: lol I didn't realize
they had 'trialware' like
that
thestringpuller: asciilifeform: i made an app, called
the asciilifeform
turd counter
decimation: all of which is abused by
the vendor
tools & magically wedged with vendor ip
decimation: yeah,
that's pretty much
the case.
the vhdl codebase is littered with 'don't
touch
this' crazy code
decimation: it can be done, it just
takes many man-months of experimentation with a particular set of hardware
decimation: I've heard from folks who have
that it is a pain in
the ass
decimation: yeah w.r.t. exact
timings, refresh rates,
things
decimation: who knows if
the authors had access
to such knowledge
decimation: asciilifeform:
there's probably an nda'ed
talmud of errata
that is supplied
to
the actual chipset dealers
decimation: ideally one would find a simultaneous set of 'hits' over an area so one could backtrack
the cosmic rays
decimation: asciilifeform: re: ecc dram <<
the paper claims
that
they can cause so many errors
that it overpowers 'correct one detect
two' style ECC dram
decimation: slur <<
that's
the dumbest
thing I've heard yet
thestringpuller: "The richest 500 addresses have continued
to accumulate bitcoin
through all
the highs and lows."
cazalla: really just seems a way
to scam donations
Adlai: oh crap,
they slapped a GPL on
the null codebase. now every new project must be GPLed
cazalla: i remember reading about
these u99 guys, have another project named coinmesh
Adlai: hm. haven't poked around
this corner of
the internet much lately
Adlai: i'm almost curious
to see what
this download is
Adlai likes how
they
talk about it in present
tense,
then later ask for money so
they can build it
cazalla: thestringpuller: I guess it
technically is already XMas for cazalla <<< 830am xmas morning but still, cuppa
tea and read logs before my first family xmas opening gifts
dignork: jurov:
thanks for
the link, haven't read
the actual method before, it's awesome.
decimation: at any rate, it's proof of
the kind of error against which asciilifeform regularly pontificates,
that is, a hardware error
that is known only
to
the vendors of
the chips
dignork: Oh, reading, even with noise, border cells might be usefull
though, haven't seen it.
dignork: so you have some more
than frequent pattern, it should match
the actual data
that you want
to write.
dignork: chances of sucessfull execution drop
to 0
dignork: we cause a random pattern error at
this position...
jurov: why not? if js in certain version of firefox can reliably cause fast repeated reads at address X,
thus affecting addresses Y,Z
dignork: so it normally cannot read your /dev/whatever
to check
the physical location, but sure, it's potentially DOS/crash, not an effective code execution.
decimation: certainly
the js memory is not randomly moved every context switch
jurov: js could corrupt browser core memory few pages away in
this scenario
decimation: dignork: are you implying
that javascript doesn't use ram?
jurov: because
there are clever interleaving schemes
to allow for faster reading
dignork: well, sure, but
these reads need
to happen nearby executed code, which by random error
turns into something executable, etc. Just can't construct any scenario it realisticly happens. But I might be wrong.
jurov: there's certainly a way how
to remotely cause already present software
to repeatedly read memory
dignork: well, same difference, you still run on his machine for
this.
dignork: well,
the
thing is, if you already can write into his memory, at very specific locations, you probably already running
there :)
decimation: umm, you can corrupt
the victim's memory by executing a loop?
decimation: note
that ECC is only a partial mitigation
dignork: decimation: cool paper, scary, otherwise I didn't bother
to calcualte probabilities for uncontrolled random scenario, or non-DOS attack vector.
decimation: asciilifeform: look at
that, some academics actually studying hardware
gribble: Bitstamp BTCUSD
ticker | Best bid: 322.76, Best ask: 323.91, Bid-ask spread: 1.15000, Last
trade: 323.93, 24 hour volume: 6248.93897115, 24 hour low: 322.0, 24 hour high: 338.99, 24 hour vwap: 332.111093959