A trust boundary is a location in your code that you assume that you can “trust” the calling code not to pass junk in the parameters or attempt something malicious. Within an single executable with no external interfaces pretty much all the code can trust it’s caller, but in a distributed application this is not the case. We have all seen distributed applications (which I’m defining in this context as any application that uses external code located in a separate location, for example local DLLs, web services, etc) that have code in the external resources that simply trusts the caller to provide all it needs and that it has a non malicious purpose with pretty much no security or validation whatsoever.
Well, I’m home from my trip. Still a little jet lagged even though I slept about ten hours last night to try to recover. We got in around 1:00 am on Monday morning, but that had been around 7:00 am for us while in the U.K. and we didn’t get much/any sleep while in transit. Pretty long day….then waking up on Monday and having to drive to some of my in-laws to get our dog in Columbus didn’t help (but it was great that they kept him for us).
Shrek 2
Now this was a movie I had been looking forward to. I really liked the first one. The cast is great and the animation is excellent. They pulled of another hit in my opinion. The successful use of pop culture references and double edged humor from the first movie was continued with the second.
The premise of the second film is that Princess Feona’s parents have requested to meet the new husband (Shrek).