Jump to content
Not connected, Your IP: 3.147.62.99

Leaderboard


Popular Content

Showing content with the highest reputation on 02/23/23 in all areas

  1. 1 point
    Staff

    New 1 Gbit/s server available (CA)

    Hello! We're very glad to inform you that a new 1 Gbit/s full duplex server located in Vancouver (Canada) is available: Ginan. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Ginan supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Ginan Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team 
  2. 1 point
    nexsteppe

    Google search not working with AirVPN

    I mostly use Kagi, nowadays, so now I pay for search just as I pay for my email and VPN. I don't feel I can trust free search engines any longer—maybe this was always the case, and I was just gullible or dumb before? I'll confess to actually being satisfied with DuckDuckGo for years, using only using Yandex Images occasionally to fill in that gap. I still occasionally use DDG's HTML or Lite (no JS) sites on my mobile and in Tor Browser. But their conduct increasingly bothers me, and I'll admit they've never seemed particularly competent. Now that DDG's results have become much worse and the engine mostly ignores quoted search keywords ("verbatim" searches) while making ads more prominent and almost visually indistinct from results, it's hard for me to even take them seriously. I was honestly less bothered by their compromise with Microsoft than I was their lack of transparency about this and other matters before being confronted by journalists. Screw that. Startpage has a long history of hostility toward VPN and especially Tor users, and they've never been particularly forthcoming about their relationship with their now owner, System1. They probably mean well, but I can't help but feel they're not better than DuckDuckGo.
  3. 1 point
    Staff

    Quantum computing and Encryption

    @kbps Hello! Not really, because the feature is included in our WireGuard setup since the very beginning, when we offered WireGuard as a beta feature some years ago. If you want more information, please see here: https://www.wireguard.com/protocol/ In this way we can implement a recognized as quantum-resistant cipher if needed, according to our customers request . You may ask why don't you pick one PQ cipher right now? You already configured the most part! We have excellent reasons not to do so right now: It's premature. In spite of the hype, currently a quantum computer doesn't work for any practical purpose to break even the weakest encryption algorithm and in the last 40 years or so the expected date to have a working quantum computer capable to perform something more than basic arithmetic have been shifted decade after decade. Research has progressed more slowly than ultra-optimists expected. To break RSA 2048 in a reasonable time a rigorous simulation shows that you need at least 1 million (probably up to 10 millions) of physical qubit (you need probably at least 10'000 logical qubits, and due to the astronomically high error rate of qc, to rely on them you need ~ x100 physical qubits). Nowadays the biggest companies are struggling to beat 433 logical qubits qc (IBM promised 1000 logical qubits machine within the beginning of 2024). It hits performance. Some promising PQ ciphers use 64 KB or larger public and private keys and you will notice a performance hit if you have a Gbit/s line and you're used to the high performance our infrastructure is normally capable to provide. The load both on server and client will increase. It exposes our customers to unnecessary risks. Post-quantum algorithms are far less well-studied. Any PQ algorithm, that today is considered safe, can be compromised tomorrow by "classical" computes.. It happened already to SIKE, which before the spectacular fall was considered one of the strongest and best algorithm for Diffie-Hellman key exchange in a post-quantum world. It was cracked in a matter of hours a few months ago with a program running in a single thread of a single core of a desktop CPU. SIKEp434 was broken within approximately an hour, SIKEp503 cracking required 2 hours, SIKEp610 8 hours and SIKEp751 21 hours. See also https://www.securityweek.com/nist-post-quantum-algorithm-finalist-cracked-using-classical-pc/ So, we have the infrastructure ready to add a PQ cipher, when and above all if it will be necessary, without exposing you to risks of cracking by classical computers and/or "performance hit for nothing". Kind regards
×
×
  • Create New...