| Summary: | app-crypt/pinentry-1.0.0-r2: pinentry-curses SIGSEGVs after typo'd passphrases | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matt Rechkemmer <matt+bugzilla> |
| Component: | Current packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | crypto+disabled |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Matt Rechkemmer
2018-02-24 18:07:08 UTC
>
> Happy to help troubleshoot further, but I'm a bit out of my depth. strace
> wasn't particularly revealing. I think the problem lies with pinentry, but
> I'm not sure where specifically.
If pinentry SIGSEGVs , can you try to produce a backtrace using a core dump and gdb? (see ulimit -c unlimited and man gdb, mainly you start it up and do a "bt")
To try pinentry directly, use e.g
/usr/bin/pinentry <<<GETPIN
That should hopefully help debugging without going through agent .. And to have it said, use a test password and not real one...
Need more info to debug, please reopen if adding the requested information |