Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
en:archiv:tut:basics:ssl [2024/01/28 11:58] – Automatic translation psycore | en:archiv:tut:basics:ssl [2024/09/23 10:39] (current) – removed psycore | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{page> | ||
- | ====== Surfing the net safely ====== | ||
- | {{template> | ||
- | |||
- | ===== Introduction ===== | ||
- | |||
- | Dangers lurk everywhere, especially on the Internet. We surf most sites without any protection worth mentioning. From a purely technical point of view, it is easy to record and read such data packets. | ||
- | To prevent this, banks etc. use so-called secure connections. What are secure connections? | ||
- | This article is about this encryption and how to recognise that it has been established. | ||
- | |||
- | Before we address this topic, we should first make sure that Windows has the necessary basic protection [[windows: | ||
- | |||
- | ===== Browser application ===== | ||
- | |||
- | ==== Features of a secure connection ==== | ||
- | |||
- | How do I recognise that the website I am about to register on is sending my data in encrypted form? There are a few criteria that must be met for a secure connection. The first should be to check the protocol. Sounds more difficult than it is: | ||
- | |||
- | - We look at the address bar of the browser | ||
- | - if there is no http:// or https:// is displayed, we click once in the address bar | ||
- | - Now the complete link should be visible | ||
- | |||
- | The standard protocol would be http, but we want a secure connection so the protocol must be https. It should look something like this: | ||
- | |||
- | {{tut: | ||
- | |||
- | So the first feature is checked: We are using the correct protocol. | ||
- | |||
- | The other features deal with certificates and the differences between them. | ||
- | |||
- | === A secure connection === | ||
- | |||
- | Now we check the certificate to see whether the browser accepts it or not. To do this, we click (in Firefox) on the blue or green coloured area to the left of the address bar. We get a window similar to this one: | ||
- | |||
- | {{tut: | ||
- | |||
- | We can see from the information for whom the certificate was issued and that the connection is secure. This is the basic protection that should be in place when sending private data. It prevents the connection from being intercepted. However, this is not enough for certain applications, | ||
- | |||
- | === A trustworthy connection === | ||
- | |||
- | Some data is so sensitive that we cannot simply rely on having a secure connection. We need to be sure that the website really is who it says it is. This is where trusted connections come in. | ||
- | |||
- | We can recognise these by the green bar in the address bar. In Firefox, for example, it looks like this: | ||
- | |||
- | {{tut: | ||
- | |||
- | This type of certificate is also called, [[wpde> | ||
- | |||
- | ===== A practical test: Is the site secure? ===== | ||
- | |||
- | All the theory is often overwhelming, | ||
- | |||
- | - Is the link to the page correct? (Phishers like to spoof the domain) | ||
- | - Does the site use a certificate to send sensitive data? | ||
- | - Is this certificate fit for purpose? (Banks only use EV certificates) | ||
- | - Does the browser return an error when checking the certificate? | ||
- | |||
- | Does it apply to smaller online shops? | ||
- | |||
- | - Read the reviews on independent review portals | ||
- | - Does the shop have a legal notice and valid contact information? | ||
- | - Does the shop have a VAT ID? | ||
- | - Are there links to this shop from trustworthy sources? | ||
- | |||
- | ===== Conclusion ===== | ||
- | |||
- | |||
- | If you stick to the tips from the practical test, you can be very sure of what sites are safe and what are not. It is important to keep your eyes and ears open and to be aware of the dangers that the Internet harbours. |