EvilZone

Thanks for the great paper on the Observer design pattern . I have not much played with design patterns but I know these are essential stuffs that the software engineering teams need to keep on implementing frequently.

Based on my understanding, we use observer pattern to notify all the depending objects when the state(s) of an object change (one to many). The example that hit my mind is the GUI system where change in background data needs to change the state of one or more GUI items.

Also, what do you think of having abstract GameState class with addObserver(), removeObserver(), and notify() as the base methods, and concrete classes that inherit GameState class and has additional methods getState() and setState(). I mean this could be useful in some scenarios.

And, How can we handle the situation where we need to send notification to yet another object when a state change in some object affects the observer object in some particular fashion.

Great paper. +1

I am not a security guru but I would like to share my understanding on the subject matter.

If you are using http or other publicly known for being insecure protocols (such as ssh v.1), the ISP can easily dissect every packet from your network to ISP. Then, the job of ISP becomes way easier. Moreover, there are several attacks such as DNS cache poisoning, misconfiguration in ISP's equipments/setups that can be planted by outside hackers who can then intercept your packets.

If you are using TLS, then I would say you are quite safe unless either your browser trusted certificate is messed somehow or the attacker(s) have control over the Certificate Authority. Please note that SSL/TLS is nothing but an additional security layer for transmitting data. It allows only the two ends (source and destination) to see the data. However, it does not ensure other form of attacks in either the server or in your system. The use of TLS basically ensures two main things: it ensures that you are talking with the right machine at the other end, and it ensures that no one can eavesdrop and gain access to the data you are sending/receiving.

That is to say, the ISPs can at most gather what I would like to call meta-information about your packets such as source, destination, and amount of traffic, and nothing more. Hence, I find the possibility of reading your data to be thin. Of course, if you are more paranoid and can't trust your ISP, you could employ the encrypted tunnels/vpns to proxy all your traffics.

Btw, I don't think SSL has any such secret password thing. SSL is based on the public key cryptography and employs two asymmetric keys (Public and private keys). The idea here is that anything encrypted with a private key can only be decrypted by the public key and vice-versa.

Thanks for your input, I will send you a pm when I have some code so you can look at it if you want?

Well sir I'm out of reach from Internet for a while. PM me and I'll have a look on your script

Well if its the non-programming savvy person, you could even install the remote administration tools initially rather than doing through the PHP script later on. Plus you could add a hidden administrator account and setup the remote desktop connection to the computer.

Or you could hide the obfuscated PHP code somewhere in the file which your end user would access the most (eg. index.php). Something that would trigger based on some POST or COOKIE. Don't use GET (eg. index.php?shell=1 ) as the HTTP logs would keep the full URL with all the query parameters. Easy method would be to use COOKIE (eg. if COOKIE['shell'] is set, the shell access would be given to you).

Respect!!!
Bellard is the guy who developed FFMPEG, QEMU, and TinyC Compiler. He is the one to develop LZEXE at the mere age of 17.

Well, VS C++ Is both an ide and compiler. So what  do you suggest?

Well, I guess cl is still the command line tool for compilation in VS C++ so if you do cl /EHsc your_code.cpp, then that will be better. My point is, try to familiarize yourself with different flags the compilers back end leverage to you. Most often, the GUI tend to impose just the widely used flags and sometimes, you might need to use different other switches so I suggest to use CLIs when you're learning.

Once you are comfortable with the compilation options, you can then freely use the IDEs.

Well if you are using Code::Block or VS12, you should know that they are IDEs, not the compilers. Think of them like a wrapper around the all those compilation processes your source code must go to get translated into the target machine code. I must say that if you are learning, do not use these IDEs. Well IDEs have their own benefits such as code profiling, refactoring, debugging front ends, intellisense, deployment mechanisms, etc. bundled within them. But, as you said, you are starting to learn C++, I would say, go for g++ (& I guess you can use g++ on Windows through Mingw or Cygwin). As for text editor, GNU Emacs or Vim should be more than enough. Notepad++ is also a great text editor. Though they don't provide the code completion features like the IDEs, this will help you keep information in your memory.

And, you must understand the difference between IDEs and Compilers so you should google the difference.