Easier... right... Because typing the 's' after http increases the complexity THAT MUCH.
However.... Since I exist in that no-mans land between upper and worker bee, here's what I suggest: Design a solution that secures the portal; hopefully with minimal changes visible to the customer, perhaps with increased functionality. Yes, it may take longer than simply pulling the plug, but spearheading a project like that produces an end result (improved functionality with security) increases your value to the company and creates an image of you that says you are a problem solver not a problem creator or simply a naysayer. And problem solver = increased value = resume fodder = $$$$ Craig > > > On Oct 12, 2009, at 10:24 AM, Soft Reset wrote: > > > Without spilling details, I told the IT team to remove an exposed > > web portal from the internet as it was not SSL protected and the > > password was easy enough to be found in my kid's "My First > > Dictionary". This is the response I got back from our "top guy": > > > > "Many people need access to the web portal. Remember that one of > > the objectives is to develop a strategy > > for the customer. Easier access, not harder, should be the goal." > > > > I laughed. How about you? > > > > > > --SR6 > > _______________________________________________ > > Pauldotcom mailing list > > [email protected] > > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > > Main Web Site: http://pauldotcom.com > > _______________________________________________ > Pauldotcom mailing list > [email protected] > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > Main Web Site: http://pauldotcom.com >
_______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
