Skip to main content

Posts

Showing posts with the label encryption

Ahmia Search Tor Hidden Services : Afmia fi Tor search engine

            Ahmia's mission is to create the premier search engine for services residing on the Tor anonymity network. In doing so, we hope to share meaningful statistics, insights, and news about the Tor network and the Tor project. Contributors to Ahmia believe that the Tor network is an important and resilient distributed platform for anonymity and privacy worldwide. By providing a search engine for what many call the "deep web" or "dark net", Ahmia makes onion services accessible to a wide range of people, not just Tor network early adopters. Juha Nurmi, Ahmia Project Leader juha.nurmi@ahmia.fi ) is the founder and project leader of the Ahmia search engine project. He is a security researcher, and has been involved in numerou

How encrypted email works?

From holiday photos to our purchasing history to personal correspondences, our emails contain a great deal of sensitive information. It is therefore vital to keep your inbox and messages secure. This is more difficult than it first appears, as email was invented and widely adopted in the early days of the internet before many of today’s security best practises were developed. As with all digital content, the best way to keep emails secure is by using encryption — complex algorithms that prevent anyone from reading the content unless they have the correct encryption keys.  In this article, we explain the different types of encryption that most email services use to protect your messages and what ProtonMail does to add an extra layer of security and privacy. How email is encrypted Most modern email services encrypt emails in two ways: They use TLS/SSL encryption in transit. This is the same encryption used to secure HTTPS websites, and it is

Better SSH Authentication with Keybase

  The most common way of handling SSH authentication is public key authentication. This is much stronger than simply using a password, but it creates the problem of how to securely manage changes to SSH keys over time. If ten new people join a company and five others leave, someone has to add the ten new keys to each server and remove the previous five. This is a process ripe for automation. Some companies do it by centralizing storage of SSH public keys and baking them into images as applications are deployed. But SSH supports another way of handling authentication: Certificate Authorities (CAs). With an SSH CA model, you start by generating a single SSH key called the CA key. The public key is placed on each server and the server is configured to trust any key signed by the CA key. This CA key is then used to sign user keys with an expiration window. This means that signed user keys can only be used for a finite, preferably short, period of time before a