paradox404
Active Member
- Messages
- 713
Sorry about the late reply to this, I have been bogged with assignments, my internet keeps playing up, and my laptop refused to boot recently.
Thanks, I'll have to re-download truecrypt, I will have a go implementing that in TDOS, it seems alright. One thing I noticed though is that every time I attempt to harden my host OS it strangly keeps malfuntioning. I know there is no issue with my drives, as they are in perfect health and the ones I use are brand new. Also, I can re-install perfectly. The last time it happened, (a few weeks back) the OS refused to boot, I ended up booting into the recovery environment, and WOW it worked, I ended up doing a bit of investigating and found the graphics were at fault, but when I digged deeper I found the problem was actually that some of the critical files relating to it had been deleted. Then again, when I checked with a rootkit scanner I found a false positive of sukkit rootkit, perhaps not one after all, perhaps it was NSA involvement that keeps doing this?
Stranger things happen though, a while back around the time Ubuntu started getting it's "Lenses" I was getting snail rate Internet, and I found out it was uploading something, I did a bit of searching and found that something was being sent, to CANONICAL? I turn the computer off and on 3 times, still doing it. I ended up patching all their IP's before they screwed my computer and they haven't done that since, but started the graphics "Issue", which started about a week later and has occured on ~3 completely different laptops.
_______________________________________________________________________________________________________________________________________
I thought of more features for the OS.
11.) In the event of an intrusion, the OS must be able to trace the Hacking Computer's IP Address.
NSA style approach, but without the authority, this would give me information that would be important to find out who did the hack, also so the system can determine if I am simply connecting with new hardware.
12.) The system Must be able to upload a virus to a hackers computer, if need be destroy it. Must also be able to prevent return of such virus and only ever allow it to be used on itself in either critical breach or owner initiated self-destruct.
At the moment I am trying to get my hands on a Platform independent Virus for the OS, which follows on from the above point, but if a serious intrusion is detected, the system then attacks the hacker's computer with the virus which will literally destroy it with an explosion. Any non-serious attempts might simply make the computer not work, but that really just depends how paranoid I am by the time I implement it. The Virus will also be used as a last resort for the OS itself. The OS would wipe all the systems storage, including most of the ram, in which the virus would upload itself to the remaining ram and then make the computer self-destruct, again literally. I am tossing up whether to make it affect any hardware the computer is connected to. The system would create the self destruct during critical breaches, not the hacker, but it would send a copy to the hacker as well.
Progress:
I have got 8 and 4 implemented at the moment, currently working on getting XEN to work in a CHROOT environment.
Thanks, I'll have to re-download truecrypt, I will have a go implementing that in TDOS, it seems alright. One thing I noticed though is that every time I attempt to harden my host OS it strangly keeps malfuntioning. I know there is no issue with my drives, as they are in perfect health and the ones I use are brand new. Also, I can re-install perfectly. The last time it happened, (a few weeks back) the OS refused to boot, I ended up booting into the recovery environment, and WOW it worked, I ended up doing a bit of investigating and found the graphics were at fault, but when I digged deeper I found the problem was actually that some of the critical files relating to it had been deleted. Then again, when I checked with a rootkit scanner I found a false positive of sukkit rootkit, perhaps not one after all, perhaps it was NSA involvement that keeps doing this?
Stranger things happen though, a while back around the time Ubuntu started getting it's "Lenses" I was getting snail rate Internet, and I found out it was uploading something, I did a bit of searching and found that something was being sent, to CANONICAL? I turn the computer off and on 3 times, still doing it. I ended up patching all their IP's before they screwed my computer and they haven't done that since, but started the graphics "Issue", which started about a week later and has occured on ~3 completely different laptops.
_______________________________________________________________________________________________________________________________________
I thought of more features for the OS.
11.) In the event of an intrusion, the OS must be able to trace the Hacking Computer's IP Address.
NSA style approach, but without the authority, this would give me information that would be important to find out who did the hack, also so the system can determine if I am simply connecting with new hardware.
12.) The system Must be able to upload a virus to a hackers computer, if need be destroy it. Must also be able to prevent return of such virus and only ever allow it to be used on itself in either critical breach or owner initiated self-destruct.
At the moment I am trying to get my hands on a Platform independent Virus for the OS, which follows on from the above point, but if a serious intrusion is detected, the system then attacks the hacker's computer with the virus which will literally destroy it with an explosion. Any non-serious attempts might simply make the computer not work, but that really just depends how paranoid I am by the time I implement it. The Virus will also be used as a last resort for the OS itself. The OS would wipe all the systems storage, including most of the ram, in which the virus would upload itself to the remaining ram and then make the computer self-destruct, again literally. I am tossing up whether to make it affect any hardware the computer is connected to. The system would create the self destruct during critical breaches, not the hacker, but it would send a copy to the hacker as well.
Progress:
I have got 8 and 4 implemented at the moment, currently working on getting XEN to work in a CHROOT environment.
