SRWare Iron - The Browser of the Future SRWare Iron: The browser of the future - based on the free Sourcecode "Chromium" - without any problems at privacy and security Chrome thrilled with an extremely fast site rendering, a sleek design and innovative features. But it also gets critic from data protection specialists , for reasons such as creating a unique user ID or the submission of entries to Google to generate suggestions. SRWare Iron is a real alternative. The browser is based on the Chromium-source and offers the same features as Chrome - but without the critical points that the privacy concern. We could therefore create a browser with which you can now use the innovative features without worrying about your privacy. We want our users to participate in our work and make the browser free to download under the name "SRWare Iron" into the net. What does Iron makes different? * Chrome and Google are registered trademarks of Google Inc.
Greasemonkey Strict Transport Security (The Chromium Projects) . HSTS allows a site to request that it always be contacted over HTTPS. HSTS is supported in Google Chrome, Firefox 4, and the popular Firefox extension. The issue that HSTS addresses is that users tend to type at best, and omit the scheme entirely most of the time. However, HTTP is insecure. An HSTS enabled server can include the following header in an HTTPS reply: Strict-Transport-Security: max-age=16070400; includeSubDomains When the browser sees this, it will remember, for the given number of seconds, that the current domain should only be contacted over HTTPS. Preloaded HSTS sites There is still a window where a user who has a fresh install, or who wipes out their local state, is vulnerable. If you own a site that you would like to see included in the preloaded HSTS list, start sending the HSTS header and then contact: A selected subset of the members of the preloaded HSTS list:
Rapporteur de compatibilité de module Exporter vos bookmarks Delicious vers Chrome ou Firefox. | Kimly <div class="greet_block wpgb_cornered"><div class="greet_text"><div class="greet_image"><a href=" rel="nofollow"><img src=" alt="WP Greet Box icon"/></a></div>Hello there! If you are new here, you might want to <a href=" rel="nofollow"><strong>subscribe to the RSS feed</strong></a> for updates on this topic.<div style="clear:both"></div><div class="greet_block_powered_by">Powered by <a href=" title="WP Greet Box WordPress Plugin" style="text-decoration:none;">WP Greet Box</a><a href=" title="WordPress Plugin" style="text-decoration:none;">WordPress Plugin</a></div><div style="clear:both"></div></div></div> Exporter vos bookmarks sur Delicious : - Connectez-vous sur votre compte ici Importer dans Chrome : - Et cliquer sur ouvrir. Importer dans Firefox :
The SeaMonkey® Project - CometBird BrowserCheck – Testez la sécurité de votre navigateur internet BrowserCheck – Testez la sécurité de votre navigateur internet Vous voulez savoir si votre navigateur internet est sécurisé ? Et bien connectez vous à ce scanneur en ligne baptisé BrowserCheck et créé par la société Qualys qui vous dira si vous surfez avec un navigateur bourré de failles et de plugins périmés. Mon test avec Chrome... Et mon test avec Firefox ! Super pratique en tout cas, car il propose les accès direct aux derniers plugins à jour. [Source] Vous avez aimé cet article ? The Pale Moon Project homepage - Cyberfox NPAPI deprecation: developer guide - The Chromium Projects We recently updated our plans to phase out support for NPAPI in early 2015. This guide provides more details about what to expect and alternatives to NPAPI. Starting in Chrome 32—expected to reach the Stable channel in mid-January 2014—when a user visits a page with a non-whitelisted NPAPI plug-in, they will see: Note that there will not be a yellow info bar (i.e. "drape") at the top of the page. This behavior is similar to existing behavior when all plug-ins are blocked by default (“Settings” => “Advanced Settings” => “Privacy - Content Settings” => “Plug-ins,” select “Block all,” and then load, for example, January 2015 Currently Chrome supports NPAPI plugins, but they are blocked by default unless the user chooses to allow them for specific sites (via the page action UI). April 2015 In April 2015 (Chrome 42) NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. September 2015 Security