Re: Changing encryption backend (discussion)

Thanks for all the replies regarding the existing fork of pass. Did not know that, so consider this issue closed. > Am 18.01.2023 um 14:00 schrieb Louis Bettens : > > Hi, > > There already exists a fork of Pass that uses age as a backend.[1] Thus > there's no point in reinventing that in our br

Re: Changing encryption backend (discussion)

>> the other day I was thinking about whether it might be time to >> replace GPG with another backend. age [1] > > Even if Pass were to support Age as an alternate backend, why replace > GPG? None of the reasons given is compelling enough for those already > using GPG to switch. Sure, if you are

Changing encryption backend (discussion)

Hello to all, the other day I was thinking about whether it might be time to replace GPG with another backend. age [1] is written in Go, seems to follow a similar philosophy as e.g. WireGuard (reasonable algorithms, no unnecessary configuration, ...) and is accepted by the community (about 12.7k s

Question about patch and Software to be added to clients

Hi, I have two things on my mind. First, I wrote a patch some time ago that makes pass significantly faster under macOS. Unfortunately this patch has not yet been merged with the repo. Is there any chance that this will happen? In fact, there are 5 patches that I submitted in October (https://

Introducing Passafari: https://github.com/adur1990/Passafari

Hi, I just wanted to announce, that I wrote a Safari App Extension, which is able to autofill credentials in Safari in macOS. It is a very first beta, so be prepared for bugs. But my colleague and me use it for several days now and it works pretty well. It can be found on my Github page: https

Re: [PATCH 5/5] Move gnu-getopt path infering into own function

Any changes for this patch series to go upstream or do i have to patch it on my own on every update? ___ Password-Store mailing list Password-Store@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/password-store

Re: Safair browser extension

To the best of my knowledge, there is no extension for Safari, but I’m currently writing one. Unfortunately, it is not a trivial task due to a hell of a lot of restrictions introduced by Apple. As soon as I have a working beta I will publish it and introduce it via this mailinglist.

Re: [PATCH] Speedup pass on macOS and brew

As there were no more complaints, I guess my patch is ok? I will tag it [PATCH] and hope, that it will go upstream. Part 1: Use three assumed default paths for gnu-getopt lookup brew --prefix gnu-getopt will allways make some git lookups which may take longer, depending on your internet connecti

Re: Speedup pass on macOS and brew

All right, looks like I have found a good solution thanks to my teammate Jonas. It’s a multi-staged lookup. First, look in $PATH, if it’s not there, try to get it from brew, then from macports. Additionally, I implemented a lookup for macports so that we do not assume the default path any more.

Re: Speedup pass on macOS and brew

So, I have a new version pasted below. Now, I set $PATH for the script containing the three possible default paths. If we then find, that the macOS default getopt is used, we start the lookup as proposed before. There is still some not so nice thing. This will only speed up things for users us

Re: Speedup pass on macOS and brew

> Well, on my installation I have: > > brew --prefix gnu-getopt > /Users/jlaffaye/homebrew/opt/gnu-getopt Okay, fair enough. Then we should have a fallback. > I also want to suggest adding an environment variable to specify the location > to not run this discovery step, so people in my situati

Re: Speedup pass on macOS and brew

> The only thing that annoys me with the code above is that we always execute > brew, though technically the overhead is the same or less than guarding it > with a command -v brew statement (less for people who have the executable). Okay, I see your point. Maybe we can ditch this all together?

Re: Speedup pass on macOS and brew

> Am 23.10.2018 um 13:35 schrieb Allan Odgaard : > > On 23 Oct 2018, at 18:11, pass-maillingl...@artursterz.de > wrote: > > But you are right in one part, Amir. Just because brew or macports are > installed doesn't mean that gnu-getopts was installed w

Re: Speedup pass on macOS and brew

> Both of your suggestions assume that if Homebrew or Macports is installed, > then > getopt must be installed by that tool, which may be wrong. I’m not sure if you are right. To break it down, the original version does the following: First, it tries to get the path from brew. If that fails,

Re: Speedup pass on macOS and brew

Thank you for your review You are right, your code looks much cleaner and does not contain redundancies. I also think that testing for exit status is better, since this also does not spawn the test process. I created a git diff, which would be nice if it goes upstream. diff --git a/src/platfor

Speedup pass on macOS and brew

Hi, currently (and as I can tell also in the past, see [1],[2],[3],[4],[5]), brew —prefix is really slow (see the example output below), which makes it somewhat annoying using pass on macOS. I hunted this down and found that the problem is the following: brew runs git rev-parse --short=4 --ver