Door Anoniem: Door Anoniem: Door Anoniem: Door Anoniem:
With this new app release we switched to the NIST standard ML-KEM from the earlier Kyber standard, but this is essentially a minor revision of that standard.
Bron: https://mullvad.net/nl/blog/quantum-resistant-tunnels-are-now-the-default-on-desktop
Want gloednieuwe implementaties gebruiken draagt geen enkel risico ...
Begrijpelijk dat een VPN verkoper mee moet lopen in de hype, maar je mag ook zelf wat nadenken.
Het is open-source:
https://mullvad.net/en/open-source
U kunt zelf de broncode controleren.
Het is geen hype.
Zeker nog nooit zelf een serieuze broncode review gedaan.
Toen ik werkte bij een Grote Machinebouwer in het Zuiden des lands, was de metric voor een review: 150 regels per uur.
En dan wist je al van de hoed en de rand qua implementatie, zonder context is sourcecode n.l. niet goed te begrijpen.
Voor iets geheel nieuws zal het aantal regels/uur nog veel lager liggen. En dan moet je ook nog van alle
gebriukte algoritmes en technieken en standaarden weten hoe ze in elkaar zitten.
Nee, open source reviews doet niemand, want de effort is te groot en het resultaat te laag,
bovendien gaat iemand anders met de opbrengst aan de haal. Intern in een bedrijf is dat natuurlijk
anders.
Methods for Viewing Source Code
There are several ways to view the source code of an open-source piece of software. The method you choose will depend on the nature of the software and your level of expertise. Here are some common methods for accessing source code:
Visit the Project Website: Many open-source projects host their source code on websites such as GitHub, GitLab, or Bitbucket. These platforms provide a user-friendly interface for browsing through the codebase, viewing files, and tracking changes. Simply visit the project’s website and look for a link to the source code repository.
Clone the Repository: If the project is hosted on a version control system such as Git or SVN, you can clone the repository to your local machine. This allows you to have a local copy of the codebase, which you can explore, modify, and contribute to. To clone a repository, you will need to have the appropriate version control software installed on your machine.
Use a Code Browser: There are several code browsing tools available that can help you navigate through source code more easily. Tools like Sourcegraph, OpenGrok, and Understand provide features such as code search, syntax highlighting, and code navigation. These tools can be particularly useful for exploring large codebases with multiple files and directories.
Read Documentation: Many open-source projects provide documentation that explains the architecture, design decisions, and coding conventions of the software. Reading the documentation can help you gain a better understanding of the codebase and its functionality.
Ask for Help: If you are having trouble accessing or understanding the source code of an open-source project, don’t hesitate to ask for help. Many projects have active communities of developers who are willing to provide assistance, answer questions, and offer guidance.
Tips for Navigating Source Code
Navigating through the source code of an open-source project can be a challenging task, especially if the codebase is large and complex. Here are some tips to help you navigate through the code more effectively:
Start with the README: The README file is typically included in the root directory of a project and provides an overview of the software, its features, and how to get started. Reading the README can give you a high-level understanding of the project and its structure.
Explore the Directory Structure: Familiarize yourself with the directory structure of the project to understand how the code is organized. Look for directories such as src (source code), tests (unit tests), and docs (documentation) to get a sense of where different components of the project are located.
Search for Keywords: Use the search functionality of your code editor or code browsing tool to search for keywords, function names, or classes that are relevant to the feature you are interested in. This can help you quickly navigate to the relevant parts of the codebase.
Follow Dependencies: Pay attention to dependencies between files, classes, and modules in the codebase. Understanding how different components of the software interact with each other can help you make sense of the overall architecture.
Read Comments and Documentation: Comments and documentation within the source code can provide valuable insights into the purpose of a particular piece of code, its intended behavior, and any constraints or assumptions. Be sure to read comments and documentation to understand the code better.
Experiment and Test: Experiment with making small changes to the codebase and see how it affects the behavior of the software. Testing your changes can help you gain a deeper understanding of how the code works and how different components interact with each other.
Collaborate with Others: If you are having difficulty understanding a particular part of the codebase, reach out to the community of developers working on the project. Collaborating with others can help you gain new perspectives, learn from others’ experiences, and overcome challenges more effectively.