La séance de questions et réponses d’aujourd’hui nous est offerte par SuperUser, une sous-division de Stack Exchange, un groupe de sites Web de questions-réponses dirigé par la communauté.
La question
Le lecteur de SuperUser, David Starkey, veut savoir pourquoi son navigateur dit qu'un site Web sécurisé n'est pas entièrement sécurisé:
I was accessing Pandora via SSL and noticed a few icons by the URL. First is this exclamation point in a triangle, indicating the page is not fully secure.
Qu'est-ce qui se passe ici? La connexion de David au site Web de Pandora est-elle sécurisée ou non?
La réponse
Redburn, contributeur à SuperUser, a la solution pour nous:
This is called a “mixed content” page. From the Mozilla Developer Network (Mixed Content):
If the HTTPS page includes content retrieved through regular, cleartext HTTP, then the connection is only partially encrypted: the unencrypted content is accessible to sniffers and can be modified by man-in-the-middle attackers, and therefore the connection is not safeguarded anymore. When a webpage exhibits this behavior, it is called a mixed content page.
The statements are not contradictory, but complementary, and a little confusing perhaps. The first says the page itself is not fully secure because it contains unencrypted elements (all web browsers will notify you of this), whereas the second notes that these elements have been automatically blocked by Firefox.
If Firefox did not block the unencrypted elements, then strictly speaking, the page would not be secure.
HTTPS Everywhere does not guarantee a secure connection. It will only try to force HTTPS whenever it is available; if it is not, then there is nothing a user or browser can do about it outside of blocking the unsecure content.
Avez-vous quelque chose à ajouter à l'explication? Sound off dans les commentaires. Voulez-vous lire plus de réponses d'autres utilisateurs de Stack Exchange doués en technologie? Découvrez le fil de discussion complet ici.