Hmm, can you elaborate on why this is so? I only know that Windows 8 is very integrated with the cloud, but if you disable all the options in privacy settings it should be fine? And the TPM controversy of course, but is there anything else?
I would really love to see you make a Windows 8 version
The BIOS idea, I like it. However I have not nor know anyone who have had that problem. But still it's a good idea
Well here is the interesting little nugget that you may like to hear about, there are some malicious software injection packages which deliver payloads that target the firmware and BIOS of common brands of motherboards and chipsets which corrupt the firmware / BIOS in such a way so as to create the perfect environment for further malicious activity. Whether by creating shadow volumes, altering the core features of the motherboard, or otherwise diverting data toward some purpose not user approved, all without blatantly damaging the system's operational ability or frying the system outright just so that a person who is unaware of the demons under the hood can provide all sorts of fantastic information for black hats.The BIOS idea, I like it. However I have not nor know anyone who have had that problem. But still it's a good idea
There was such a quickening rush as I found myself reading some excerpts aloud to my wife whom I can see, not far away, sitting at her desk in another room. ..which actually sounds quite appealing!!
Thank you for sharing your excitement, and the latest advancements of your team, before and after the bar-be-que, n.nvt.
Additionally, the comments of Anupam, Plasmadragon, Kram.., Cch 123, and your replies, have made this an enthralling thread!
Am I understanding correctly that even as 'dedicated attacks do not usually apply to home computers..', with the release of the FMA Windows Live CD, we can be thoroughly battened down and safe come Hell or High water Hacking?
..which actually sounds quite appealing!!
Thank you, n.nvt, for your far reaching depth of response and explanation. In understanding the scope of organized hackers, it seems fitting to compare response readiness and how damage is dealt with when natural disaster occurs. Knowing such an event is rare is merely a component of the larger reality that it simply cannot be stopped. So, in a similar circumstance, the ability to respond to such devastation lies, as you've vividly illustrated, in the required ability to repair theWhat do you mean with this?:
Am I understanding correctly that even as 'dedicated attacks do not usually apply to home computers..', with the release of the FMA Windows Live CD, we can be thoroughly battened down and safe come Hell or High water Hacking?
I am not sure what you are trying to say but if it is what i think you have to realize that my software is not a protection its a tool for "AFTER" a hack/malware or cybercrime event.
However due to the nature of my software and the availability of factory firmware scripts the program can repair rootkit and dedicated variations added by a attacker which usually are undetected by traditional protection as we are talking about chipset level firmware which is normally not accessible by normal software.
That said in order to gain access to these deep level data storages you need much more then just a malware or simple hack attack.
So its reasonable safe to say that a home user will never get in contact with such high level attacks and modifications as its way beyond the scope of traditional hacking clubs.
And to be clear here these additions i made a based upon Asian hacking dangers which are 9/10 times governmental sponsored. And if its done by a normal hacking club then its rare..
The aim is not to protect, but the aim is to see what happened within the system regardless the origin, and to make sure the system can be repaired from such attacks and read the actual changes made by a third party regardless of technological level we need to go deep. And having original factory BIOS and firmware blueprints within the program is a major leap as it will 1 vs 1 log the changes.... in detail. And thus enable true forensics.
As this is the only way to be able to log beyond the point of what normal cybercrime can do...
Cheers
damage that's been done. Yes. I see more deeply your lesson: "OEM BIOS, firmware blueprints within the program, 1 vs 1 log of changes, and enabling True forensics...beyond the point of the norm."
Any updates on the windows 8.1 version for home users? You make me feel like "downgrading" to windows 7.....
Really great work Nico.
Thank you, n.nvt, for your far reaching depth of response and explanation. In understanding the scope of organized hackers, it seems fitting to compare response readiness and how damage is dealt with when natural disaster occurs. Knowing such an event is rare is merely a component of the larger reality that it simply cannot be stopped. So, in a similar circumstance, the ability to respond to such devastation lies, as you've vividly illustrated, in the required ability to repair the
As the Character, Neo, said in the "Matrix", "Whoa-OH!!"
