Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

passff retrieves empty password from v1-pre-release-11 and on #43

Closed
tampakrap opened this issue Oct 9, 2014 · 2 comments
Closed

passff retrieves empty password from v1-pre-release-11 and on #43

tampakrap opened this issue Oct 9, 2014 · 2 comments

Comments

@tampakrap
Copy link

passff in versions v1-pre-release-11 till 13 seems to malfunction.

  • For structure: file "example.com" and contents: first line the password, second line "username: myuser", I get from passff display dialog: username: example.com, password:
  • For structure: example.com/myuser, containing only one line with the password, I get from passff display dialog: username: myuser, password:
    The goto functionality works fine in both the above cases.

My configuration is:
password input names: passwd,password,pass
login input names: login,user,mail,email,username,wpName,log,name,u
password field names: passwd,password,pass
url field names: url,http
login field names:login,user,id,username

I was also able to reproduce in a clean environment. Let me know if you need further debug info

@jvenant
Copy link
Collaborator

jvenant commented Oct 13, 2014

I just can't reproduce your issue.
Both cases work for me.

"password field names" property contains a comma (",") separated list of all the possible field names to retrieve the password. It is used for the two structure modes

Same behavior farm "login field names" but for the login of course.

Please could you check again that the values you put in those properties match exactly the ones use in pass. Especially, be sure to not put spaces between comma.

If it still doesn't work, could you also try with some simplest fields lists

@tampakrap
Copy link
Author

I never managed to figure out the issue, probably some connection issue with gpg agent. Either way, I'm closing it because right now I am on gpg 2.1 (where I filed a different issue) and I can't reproduce this one any more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants