Submission + - IE Security Flaw Exposes Your Cookies (winbeta.org) 2
This exploit is being referred to as "cookiejacking" and apparently is possible in any version of Internet Explorer under any version of Windows."
One of the greatest things about virtualization is that you can give all your devs the same setup just by copying a VM to their physical machine.
Copying a vm to all of his devs *is* a violation of the MicroSnot EULA. If it was an Ubuntu, Debian, CentOS or the like, it is almost expected.
... and one of my jobs at the last place I worked was to create a VM with all the required software for the devs..
If that vm was a windows machine, you are a software pirate. (at least according to MicroSnot)
Originally having no experience, I got a test server up and running within a day.
Does not instill confidence If you had no experience, what fucking idiot put you in charge of 700 users email? Also, it will take a day just for security updates and patches on a new setup. Unlike you, I am in charge of a couple of exchange servers. I have a lot more issues with one exchange server than all of the Postfix, Exim and Citadel mail servers combined.
Here is what happens with an open source product:
Where's the text file for exchange settings or any windows package for that matter.
Ever tried to read dns entries or dhcp map in command line because windows wouldn't boot all the way up into GUI mode?
I didn't think so.
You can open conf files because they exist. You do not have to for hours. What was that line about no experience?
I can have a physical machine fully running apache, mysql and postfix within 3 hours fully patched and operational - WITH a GUI.
I have over 20 years experience with winnders. I don't like it anymore. I now know it to be the junk that it is.
The last time I had to wade through debugging and source code was when a crack windows dev from outside my country wrote some very bad C code.
Since we're speaking of source code. You didn't say what source code you could look at on Microsoft Exchange. Did I miss that news announcement?
Last point I'll cover.
Because you have the source code is there, you CAN compile. Obviously YOU have never compiled anything, because it's easier than logging onto a windows machine.
Why is it so hard for you? Just do these three commands:
If you are really masochistic you end up compiling your own build after you have found a bug.
Should actually read: If you are really masochistic you end up reading and agreeing to the Microsoft End User License Agreement.
Say "twenty-three-skiddoo" to logout.