Comment #22 on issue 2010 by shirishag75: Feature: An option to disable the 'Expired Certificate" warning for a specific site http://code.google.com/p/chromium/issues/detail?id=2010
True. For many FOSS projects also its not possible or they not do on some ideal reasons. Lemme give too examples totally different. 1. http://blogs.gnome.org/mneptok/2009/04/19/super-troopers/ 2. http://data.bsnl.com The 1st one as can be seen in the entry has an expired certificate The 2nd site doesn't use encryption at all. This site has lot of confidential data and it doesn't do anything about it. Now because it doesn't even use https:// most of the users wouldn't even know that all the data is being sent back and forth is in clear-text. Obviously, the 2nd one doesn't have anything to do with the feature mentioned above but I wanted to bring it to draw attention . a. That there are websites which are trying to do something, which are using the https:// protocol http://en.wikipedia.org/wiki/Https (background reading for those who don't know what its all about. ) b. Those who are doing within whatever constraints they have for providing a more secure user experience should be given carrots rather than stick. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
