home.social

#openpgpjs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openpgpjs, aggregated by home.social.

  1. NEW BLOG POST!

    In this article soberly entitled "The world's most interesting contact form", we'll learn about OpenPGP, what it is and how it works, then use OpenPGPjs, a Javascript implementation of it to send an end-to-end encrypted email, with the help of a little Rust Axum backend.

    The second part of the article talks about Proton Mail, their promises, what they entail, and how we can verify them. At the very end, there's also a quick word about the Chat Control, the EU's latest mass surveillance project.

    Check it out! zoug.fr/world-most-interesting

    #openpgp #pgp #openpgpjs #rust #axum #chatcontrol #proton #protonmail #e2ee #encryption #privacy

  2. NEW BLOG POST!

    In this article soberly entitled "The world's most interesting contact form", we'll learn about OpenPGP, what it is and how it works, then use OpenPGPjs, a Javascript implementation of it to send an end-to-end encrypted email, with the help of a little Rust Axum backend.

    The second part of the article talks about Proton Mail, their promises, what they entail, and how we can verify them. At the very end, there's also a quick word about the Chat Control, the EU's latest mass surveillance project.

    Check it out! zoug.fr/world-most-interesting

    #openpgp #pgp #openpgpjs #rust #axum #chatcontrol #proton #protonmail #e2ee #encryption #privacy

  3. NEW BLOG POST!

    In this article soberly entitled "The world's most interesting contact form", we'll learn about OpenPGP, what it is and how it works, then use OpenPGPjs, a Javascript implementation of it to send an end-to-end encrypted email, with the help of a little Rust Axum backend.

    The second part of the article talks about Proton Mail, their promises, what they entail, and how we can verify them. At the very end, there's also a quick word about the Chat Control, the EU's latest mass surveillance project.

    Check it out! zoug.fr/world-most-interesting

    #openpgp #pgp #openpgpjs #rust #axum #chatcontrol #proton #protonmail #e2ee #encryption #privacy

  4. NEW BLOG POST!

    In this article soberly entitled "The world's most interesting contact form", we'll learn about OpenPGP, what it is and how it works, then use OpenPGPjs, a Javascript implementation of it to send an end-to-end encrypted email, with the help of a little Rust Axum backend.

    The second part of the article talks about Proton Mail, their promises, what they entail, and how we can verify them. At the very end, there's also a quick word about the Chat Control, the EU's latest mass surveillance project.

    Check it out! zoug.fr/world-most-interesting

    #openpgp #pgp #openpgpjs #rust #axum #chatcontrol #proton #protonmail #e2ee #encryption #privacy

  5. NEW BLOG POST!

    In this article soberly entitled "The world's most interesting contact form", we'll learn about OpenPGP, what it is and how it works, then use OpenPGPjs, a Javascript implementation of it to send an end-to-end encrypted email, with the help of a little Rust Axum backend.

    The second part of the article talks about Proton Mail, their promises, what they entail, and how we can verify them. At the very end, there's also a quick word about the Chat Control, the EU's latest mass surveillance project.

    Check it out! zoug.fr/world-most-interesting

    #openpgp #pgp #openpgpjs #rust #axum #chatcontrol #proton #protonmail #e2ee #encryption #privacy

  6. No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.

    Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.

    Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.

    Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.

    bugs.gentoo.org/963069

  7. No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.

    Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.

    Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.

    Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.

    bugs.gentoo.org/963069

  8. No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.

    Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.

    Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.

    Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.

    bugs.gentoo.org/963069

  9. No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.

    Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.

    Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.

    Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.

    bugs.gentoo.org/963069

  10. No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.

    Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez #GnuPG (i #rnp?), z formatem kluczy "v5" — i zdaje się, że każdy inny projekt spogląda na to z politowaniem.

    Po drugie, jest #RFC9580 z formatem kluczy "v6", używany przez #OpenPGPjs, #SequoiaPGP (i inne narzędzia), ale odrzucony przez GnuPG. I wygląda na to, że jest przepychane z założeniem, że GnuPG ugnie się pod presją.

    Więc mamy dwa niezgodne ze sobą standardy, ze "wspólnym mianownikiem" w postaci zabytkowego #RFC4880; jedne narzędzia przepychają jeden standard i ignorują drugi, a inne decydują się wspierać oba, by pomóc swoim użytkownikom. A #Gentoo ostatecznie utknie z tym, co wspierać będzie GnuPG, bo potrzebujemy kryptografii, która działa na wszystkich wspieranych platformach, a nie tylko tam, gdzie Rust.

    bugs.gentoo.org/963069

  11. Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.

    So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.

    Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.

    So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".

    bugs.gentoo.org/963069

  12. Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.

    So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.

    Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.

    So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".

    bugs.gentoo.org/963069

  13. Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.

    So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.

    Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.

    So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".

    bugs.gentoo.org/963069

  14. Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.

    So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.

    Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.

    So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".

    bugs.gentoo.org/963069

  15. Okay, so please correct me if I'm wrong about the state of #OpenPGP right now.

    So first there's the former #RFC4880bis which is now pursued as "#LibrePGP", used by #GnuPG (and #rnp?), with a "v5" key format, that everyone else seem to looks "politely" at.

    Then there's #RFC9580 with a "v6" key format, used by #OpenPGPjs, #SequoiaPGP (and more) but explicitly rejected by GnuPG. However, it seems to be pushed forward under the assumption that GnuPG will yield to pressure.

    So we effectively have two incompatible standards, with a "common denominator" of ancient #RFC4880, some tools pursuing one of them with disregard for the other, and a few supporting both for the sake of the users. And #Gentoo is effectively stuck with whatever GnuPG supports, because we need working crypto on all supported platforms, not just the "Rust subset".

    bugs.gentoo.org/963069

  16. I have started pondering how I am going to handle encryption and shared data in a financial budget app I am building.

    So far I'm using and .

    Now how do I manage the encryption of each transaction while maintaining balances and aggregation of data for different budgets and spend categories.

  17. I have started pondering how I am going to handle encryption and shared data in a financial budget app I am building.

    So far I'm using #gundb and #openpgpjs.

    Now how do I manage the encryption of each transaction while maintaining balances and aggregation of data for different budgets and spend categories.

    #budget #finance #security #encryption

  18. I have started pondering how I am going to handle encryption and shared data in a financial budget app I am building.

    So far I'm using #gundb and #openpgpjs.

    Now how do I manage the encryption of each transaction while maintaining balances and aggregation of data for different budgets and spend categories.

    #budget #finance #security #encryption

  19. The German Sovereign Tech Fund supports the development, improvement and maintenance of open digital infrastructure.
    The following projects will receive funding starting October 2022:
    #OpenMLS, #curl, #OpenBGPd, #Bundler/ #RubyGems, #WireGuard, #OpenPGPjs/ #GopenPGP, #OpenSSH

    Strengthening Digital Infrastructure and Open Source Ecosystems
    in the Public Interest
    sovereigntechfund.de/en.html

    #SovereignTechFund #FreeSoftware

  20. The German Sovereign Tech Fund supports the development, improvement and maintenance of open digital infrastructure.
    The following projects will receive funding starting October 2022:
    #OpenMLS, #curl, #OpenBGPd, #Bundler/ #RubyGems, #WireGuard, #OpenPGPjs/ #GopenPGP, #OpenSSH

    Strengthening Digital Infrastructure and Open Source Ecosystems
    in the Public Interest
    sovereigntechfund.de/en.html

    #SovereignTechFund #FreeSoftware

  21. The German Sovereign Tech Fund supports the development, improvement and maintenance of open digital infrastructure.
    The following projects will receive funding starting October 2022:
    #OpenMLS, #curl, #OpenBGPd, #Bundler/ #RubyGems, #WireGuard, #OpenPGPjs/ #GopenPGP, #OpenSSH

    Strengthening Digital Infrastructure and Open Source Ecosystems
    in the Public Interest
    sovereigntechfund.de/en.html

    #SovereignTechFund #FreeSoftware

  22. The German Sovereign Tech Fund supports the development, improvement and maintenance of open digital infrastructure.
    The following projects will receive funding starting October 2022:
    #OpenMLS, #curl, #OpenBGPd, #Bundler/ #RubyGems, #WireGuard, #OpenPGPjs/ #GopenPGP, #OpenSSH

    Strengthening Digital Infrastructure and Open Source Ecosystems
    in the Public Interest
    sovereigntechfund.de/en.html

    #SovereignTechFund #FreeSoftware