The question is...
if it was an upset employee, was that person capable of routing traffic so that it appeared the traffic came from North Korea or is there actually a '3rd party' involved in all this mess?
972 publicly visible posts • joined 27 Feb 2014
Derrrrrr.....
Each phone has a unique ID built into the hardware that persists sim changes.
Just leave a SDR and pick out the ID from cell tower communication, map the patterns then switch off the ID acceptance at the tower/network....
WTF would you try to triangulate a rarely used mobile phone or try to 'jam' it?
yep....
All the time this goes on, the amount of money to be returned to the account holders slowly diminishes in 'administrator fees'.
They could have sold the coins they had and repurchased at the lower rate, thereby ensuring EVERYONE got ALL their coins back, as it is they have completely destroyed the value of the assets of the company... something NO administrator should do.
Today I found a major new customer is running Ubuntu 5 on all its web facing production servers....
(as the IT guy pointed out.... when we run update there is nothing to be updated....) (mental note to self... strong kicking in the nuts needed)
Security by obscurity........ but at least the PHP is secure....
Yep the key is 'once setup'........
I am still in the middle of an office 365 migration... it is a complete nightmare once you get up to migrating several hundred staff.
Very difficult to delete accounts if you make a mistake, cannot initially install a hundreds of users with the same password then change on login......(yep each user has to be dealt with separately...thanks Microsoft for making me type in EVERY notification email address)
CANNOT have a catch all situation to route unknown mails, almost impossible to copy messages and route through.
( FAILS on China based staff)... weird you are using encryption in Exchange--- 'get lost' messages...... but works on OSX client!!
Microsoft partner & Microsoft don't know why.......
ER no…
Nand- flash start to act 'strangely' with temp variation or increase, as do all semiconductors.
And you should consider more about what goes wrong, rather than what goes right.
go read some of the forensic papers about what a nightmare these drives are to recover data from, then imagine something goes wrong with your setup.
In 2007 I visited suppliers in China to speak directly to the manufacturers of the various controller chips……
I have 'stuff' I was working on from 2008~. In 2011 I dropped an email to members of the security community, who were working on similar concepts.
My research covered 'anti-forensics' specifically to prevent block 'cloning' of storage devices, also systems for code injection into the data stream being read from the storage partition and systems for hiding encrypted data.( all done by controller reprogram)
I had future plans for when USB allowed a device to be both a master & slave, allowing it to probe external devices connected to hubs and utilize any WIFI adaptors plugged in.
All this was 'hidden' and non-detectable from outside of the device.
Some controllers also have a 'Fucked up mode" boot loader where they can page code from the nand-flash incase the masked rom is bad during production or extra functionality is needed.
With a multi-gb nand-flash you can build a 'paged' exploit kit, no longer limited to a particular internal code size of the controller chip.
One of my pets is a 'custom' development kit that 'emulates' the Nand-flash chip allowing rapid development from RAM/Disk without having to continually tool about , instead I just replace the 'Nand-chip' download an image of the contents of the 'flash' to ram then fiddle with the USB stick controller image in ram in an attached slave computer.
The greatest 'wet dream' are the Atheros chips….., consider all the 'datastream goodness' those reprogrammable chips have access to, plus they have their own handy WIFI which is a total black box to the computer or any computer based 'security' software.
All this bullshit could be circumvented if the applications were written properly.
Encrypt ALL the data sent to the servers and keep the private keys on the users computers,
but noooooo , these scum bags don't want to do that for at least two reasons
1. They loose access to mine the data.
2. Data de-duplication, encrypted data cannot be de-duplicated thereby pushing up storage space requirements.
Afterall what's the point in having all that lovely private data and internal documents from a massive number of companies and internal government departments if you cannot mine it ?
They just want to be greedy and are attempting to use European law to stop the US government from putting customers off cloud storage thereby fucking up their massive data grab.
Complain to your government and request that they NEVER use Microsoft products that store documents on cloud servers.
I would have to take exception to at least one of the points you make reference to in your paper
'Using Storage Class Memory for Archives with DAWN, a Durable Array of Wimpy Nodes'
"Even assuming data is overwritten daily, it would take over 25 years for a conservative write endurance of 10,000 cycles to be ex-ceeded [9]. Of greater concern are the issues of read dis-turb and data retention. "
The only mention I can see of 10,000 is related to 'latency' tests[9].
'Empirical Evaluation of NAND Flash Memory Performance'
Which goes on to state ( in the next paragraph):
"Due to the high variance of the measured endurance values, we have not collected enough data to draw strong inferences, and so report general trends instead of detailed results."
More of an issue, it the fact that since this was a 'latency' test for device speed, the writes & reads would have been in a highly compact burst on a 'new'ish chip. ( even the de-soldered devices)
More worrying…
They[9] state they measure "3.2 Endurance " by:
"Program/erase endurance was tested by repeatedly pro-gramming a single page with all zeroes, and then erasing the containing block. Although rated device endurance ranges from 10^4 to 10^5 program/erase cycles, in Figure 5 we see that measured endurance was higher, often by nearly two orders of magnitude, with a small number of outliers."
So basically this 10,000 writes was performed in a burst with values of 00 & FF ( Nand flash erases to FF)
which is not a true test of an MLC device, since the test is only testing 2 of the possible 4 states the cell can store AND the test is angled to minimize read/write disturbs from adjacent cells, not to mention the two BEST values for the read/write amps. to pick out. ( I say that because the author appears to be fully aware of how MLC devices function(2.1[9]) but uses a 'non-standard' representation for his test data all '1' or '0')
There is also no mention of:
1. The Block number they choose, in their 'single' block test ( that result seems to make me think it was block 0, which all manufacturers give the highest R/W rating to)
2.The ambient conditions the tests were performed at.
3. No mention of the Read ID's of the chips tested in [9]. ( manufacturers part numbers on the case are NOT an indication of the enclosed die, they might have been all from the same manufacturer)
I would 'like' to have seen the endurance data 'test' performed with a range of test data
1. 'True random data'
2. 'Marching ones'
3. 'Marching Zeros'
Really I would have expected a far better testing regime from the paper[9], I would have some concerns about the conclusions.
That's the problem, there are too many salesmen with their bullS**t.
There is massive amounts of peer reviewed data on Nand flash failures, and it is not only related to 'wear out', or 'fade' but also read/write disturbs.
That's why I consign any 'non-peer reviewed data' to the WPB ( waste paper basket)
Examples of 'other' failure modes.
'Techniques for Disturb Fault Collapsing'
'Program Disturb Phenomenon by DIBL in MLC NAND Flash Device'
' Study of Stored Charge Interference and Fringing Field Effects in Sub-30nm Charge-Trapping NAND Flash'
'Reliability Issues and Models of sub-90nm NAND Flash Memory Cells'
Etc…Etc….
I spent a year researching die level Nand flash for a dissertation, what I found out completely shocked me, so much so I never use SSD's for critical data storage or booting my os.
ANY sort of access to the Nand Flash array causes degradation to the data on the device (randomly!!). Read/write and even drift over time ( as the level amps. start to drift, new & old data charge levels starts to drift wider apart)
One thing they don't mention is that you can loose a complete chip of data if the read amps go out of spec .
MLC is potentially the kiss of death for your data, they store 4 different binary levels in 1 cell based on charge level rather than simple 'binary'.
So rather than storing '1 or 0' they can store '00','01','10','11' in a single bit, which means your differential read/write amps have to be SPOT on to clearly distinguish the 4 levels, if the amps. go out of spec…. so does the data.
It is VERY hard to loose a complete disk drive of data( relatively speaking), and there is usually a warning, this is not the case with Nand flash.
Worse is that some 'scumbag' companies are deliberately selling defective product into the market under a 'special' brand name, unfortunately their product and details are covered under NDA.
All I can say is that I was completely shocked at what crap is ending up on the market, some of the product is only good for 50-100 writes, ( mainly crap from China, BUT the dies are from 'reputable' known companies, so the internal die ID's read as 'quality' product when queried electronically, [you can ask a Nand chip 'who made you'])
Dolphin stolen from SQL, non existent product only computer renderings
Website that shoots content faster than you can read….
"Pianokey-Technology" ( everyone else calls then card slots) "is a unique capacity expansion technology owned by Memblaze, which is applied for PBlaze3 Flash Accelerator. Its design idea is derived from the chord of piano"
What could possibly go wrong…….
Problem is , that until now the customers did not know they had been sold a Duck….
Really FTDI should just have disabled the driver after all they would be within their right, then force the USB consortium to deal with the stolen PID.
I would expect a lot of EBAY customers being ready to make claims against EBAY and PP once these new drivers get established.
"I don't know who told you otherwise but Simplified Chinese is real Mandarin."
ER…. no.
Simplified was introduced by Mao in the 50's to try and raise the level of education of the Chinese masses ( also to deny the people the ability to read past documents).
He claimed to have produced the form himself. ( are you saying that Chinese did not start writing 'real Chinese until the 50's?….. hint it is called Mandarin for a reason….)
Prior to that traditional characters were used, and if you go to Taiwan and say such things you would be punched in the face.
The true 'written form' has evolved over thousands of years, eventually stabilizing in about the 4-5 Century and were the central form used by the Emperors courts of China.
雞同鴨講
"Chicken & Duck speaking" is a rough equivalent, they say it is not used in Mandarin only Cantonese, but that is not correct, over the last 20 years there has been a merging of such terms.
It can cause all sorts of confusion in a brothel. ;-)
( Chicken =female prostitute, Duck = male prostitute)
Go check out the Hong Kong films based around his term, there are some very funny ones.
Yep…
There are just too many homographs in Chinese, any westernized system of representing the words, ends up messing you up, even just looking at the Chinese whilst learning the words is enough to prompt the correct usage.
But then all those so called experts would not be raking in millions from the various published systems.
But Traditional & Simplified do not have the same meaning( even for the same character groups) it is not always a 1:1 substitution.
" the Django project changed their documentation on database replication to remove the terms "master server" and "slave server"."
Which is the kind of politically correct shit that just needs to be told to 'fuck off'.
Are we to change all the terms in electronics as well?
Can we no longer have SPI or I2c master & slave devices
Some people think everything is about them and to them it is the same,
Because they have spent a good amount of time mentally justifying their contribution that it becomes part of them.
And attack on the idea is an attack on them directly, after all nearly every one wants to be recognized a genius.
there is EVERYTHING wrong with 8.8.8.8 & 8.8.8.4.
It identifies:
1. The network/ computer requesting a DNS lookup
2. The target.
3. with a little bit of work, it allows cookies & facebook redirects to identify individual users traffic & interests, especially if the target is using google analitics.
4. If something were to go wrong, every DNS lookup could be directed to a single location, without the safety of a randomizing selection of alternative DNS servers.
Groupwise was a complete abortion, then they added direct connection to the internet via an SMTP NLM , which blew a massive hole in the Netware security.( you could leverage text messages to send commands to the groupwise system)
Not only did the SMTP module have ZERO security, it allowed the free relaying of any messages sent to it, from ANYWHERE on the internet to anywhere.
Almost the biggest waste of money our company invested in computer systems.
don't even get me started about 'arcserve' or even 'faxserve'