secure access to web, secret exchanging, trojan/spyware-proof system

secure access to web, secret exchanging, trojan/spyware-proof system and more ...

yes. this tutorial is the right thing for ordinary people on the street to have an unbreakable system for their own secrets; it is for the protection of privacy; it is honest; and MOST IMPORTANTLY, it makes sense and feels real.

go and read it online here:
http://umbrella.name/upid/trooseid
download it in zip:
http://umbrella.name/upid/trooseid_zip

i devoted my recent weeks working on it. and my intention is help ordinary people out there, instead of yelling jargons again and again just to show "i'm professional"( though i'm professional, and there is no doubt for this )

i'll check out AO tommorrow, and be willing to answer any questions regarding this trooseid tutorial.

thank you,

die

OMFG... Grammar. Capitalization...

Quote:

---

because the attacker, most likely he's an enemy, got control over the system

---

Nope. Why are you automatically enemies? You mosty likely do not know each other.

Quote:

---

So, we need system without any trojan - a "clean" system, each and every time we do secret communication. That is: each time we are going to have some secret communication done, we must be goddamned absolutely one-hundred-percent sure that system is a clean system. That's why common client-side OS like windows xp cannot get the job done: after normally using a windows xp system for one month( one month, imagine one month full of connecting to the internet and web surfing and email reading and powerpoint shows and microsoft word document processing and msn messenger and probably some p2p software like emule, etc, etc ), no one can be sure: "my 1month-old winxp system got no trojan".

---

Nope. I'll put my XP box up against anything you have. It's cleaner and more secure.

Quote:

---

Well, one idea is: every boot is a fresh start for a read-only OS, like a system run from cdrom, like some linux live-cd, like knoppix, etc, it is as simple as:

---

Knoppix is definitely NOT as secure as Windows. Knoppix cannot be patched as readily. And what's to prevent me from running exploit de jour on Knoppix, and gaining root until you reboot? Even writing to the CD if it is a CD-RW. (Maybe a bit advanced for you.) Not to mention Knoppix is far more difficult to customize.

I'm not even going to finish reading your tutorial. It's not worth it.

The biggest problem with Knoppix and no Harddrives etc... How do you check your logs? How do you perform forensic investigations on your compromised system?

The idea that read only gives some sort of real protection is idiotic.

Once you learn how Public Key cryptography works, and does not work, and once you learn what security really is, come back and try again.

You have some interesting ideas, but lack the knowledge and experience to make things work.

EDIT: I couldn't resist.

Quote:

---

Yes. since i'm not some college-professor jerk, i'm not going to dive into some weird mathematic explanation about it

---

I bet college professor jerks passed highschool English.

SCREENSHOTS ARE NOT DIGITAL PHOTOS OF YOUR MONITOR!!!!!

Quote:

---

(i hope you know who is the private-key owner, right?)

---

I do, do you?

OH NO IT'S THE ****ING UMBRELLA CORPORATION THAT MADE THOSE ZOMBIES IN RESIDENT EVIL!!!!!!! Do you work at the hive????

Throw some positive AP's in here. I don't want this thread closed. It's going to be entertaining.

"Read-only OS". You might want to keep in mind that there is a big difference between an OS and a file system.

Wow what a waste of time. I have seen better examples of english from 5 year olds. The diagrams are like something I would draw when I was about 6 at most. You claim to be a professional, if that is the case then you should have taken a lesson or at least read a book on basic technical writing and drawing. No professional uses cursing at any point in their document unless it is a piece about degenerate language affecting society or something of the like. A piece of technical writing should be precise, use proper english and not disgust the reader. Technical diagrams should use clear straight lines and not be overcrowded by unneeded rubbish. Any screen shot's should be taken with an appropiate application, not your digital camera and be annotated with text and a clean shape around a point of interest if needed.

Quote:

---

"Read-only OS". You might want to keep in mind that there is a big difference between an OS and a file system.

---

Maybe all he did was read about it?

d0pp i agree with everything you've said except:

"OMFG... Grammar. Capitalization..."

ive seen people say "this is a security site. things like BackOraffice should not be discussed here"

but

"Grammar. Capitalization..." you're taking things WAaaaaY too far.

personally i chose not to capitalize and click "ignore" when spell check points it out (most of the time), along with some mis-spellings. are you saying i cant do that?

Quote:

---

personally i chose not to capitalize and click "ignore" when spell check points it out (most of the time), along with some mis-spellings. are you saying i cant do that?

---

Tedob, I can still read what you write, and you have never posted anything like that. Well... I sure hope you haven't.

just kidding ya d0pp!