From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Howto request an upgrade for keychain package
Date: Fri, 19 Apr 2024 13:18:45 -0600 [thread overview]
Message-ID: <7375785e-ddde-41e7-8295-a61f39058680@SystematicSW.ab.ca> (raw)
In-Reply-To: <CAL8MddULqdNgCp2923Y=jas2ttRyo+UwnkBMimvcM9T-g5iH=A@mail.gmail.com>
On 2024-04-19 08:53, J M via Cygwin wrote:
> El jue., 18 abr. 2024 20:10, J M <cesarjorgemartinez@gmail.com> escribió:
>> I'm having some problems (gpg2, and some for ssh management) with keychain
>> package: https://www.cygwin.com/packages/summary/keychain.html
>>
>> It version is 2.7.1, can be upgraded to, by example the last 2.8.5?
>>
>> It is here: https://github.com/funtoo/keychain/tree/2.8.5
> Fow now, I implement a very weird implementation to fix this (very old
> keychain version) in pseudocode:
>
> If I am inside Cygwin and keychain version is 2.7.1 then:
> curl -L -o /usr/bin/keychain
> https://raw.githubusercontent.com/funtoo/keychain/2.8.5/keychain
>
> But it is a weird workaround, you can upgrade this package? If not exists
> any security problem clearly...
The upstream repo has not been updated since 2018.
You might be better finding a more modern, secure, compatible login manager like
gnome-keyring or KDE kwalletmanager, or improved process like using known hosts
and authorized keys files to limit access.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-04-19 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 18:10 J M
2024-04-19 14:53 ` J M
2024-04-19 19:18 ` Brian Inglis [this message]
2024-04-20 8:07 ` J M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7375785e-ddde-41e7-8295-a61f39058680@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).