You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of this issues is to gauage maintainer interest in alternative encryption backends to PGP.
Would additional backends require a significant architectural overhaul?
Has there been much demand / do you have a desire for alternatives to PGP?
Two pass implementations that I'm aware of support age encryption: gopass and passage.
An age backend in this app would enable users of those implementations to use age across all devices. Which, arguably, has a slightly improved user experience to PGP. I see an age backend was asked about here #595 and here #591. But I wanted to ask more generically -- are you open to alternative backends, or would the additional project burden be more than you're comfortable with?
The text was updated successfully, but these errors were encountered:
The purpose of this issues is to gauage maintainer interest in alternative encryption backends to PGP.
Two pass implementations that I'm aware of support age encryption: gopass and passage.
An age backend in this app would enable users of those implementations to use age across all devices. Which, arguably, has a slightly improved user experience to PGP. I see an
age
backend was asked about here #595 and here #591. But I wanted to ask more generically -- are you open to alternative backends, or would the additional project burden be more than you're comfortable with?The text was updated successfully, but these errors were encountered: