https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #15 from Graham Bloice ---
That looks interesting, an ssh-agent replacement that proxies pageant. I'll
have to test that to see if it can co-exist with the ssh-agent from Git that I
normally have
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #14 from Dario Lombardo ---
(In reply to Graham Bloice from comment #13)
>
> I have that on my long list of rainy day projects.
>
"Rainy day projects" ... I like it!
For completeness, I found a code that
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Roland Knall changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #13 from Graham Bloice ---
Pageant support will require modifications to libssh, as it doesn't use a
socket interface, instead it uses a shared memory mapped file for the data and
Windows messages
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #12 from Roland Knall ---
(In reply to Dario Lombardo from comment #11)
> (In reply to Roland Knall from comment #8)
> > So I think, support for ssh-agent and pageant (putty's ssh agent) is the
> > right way
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #11 from Dario Lombardo ---
(In reply to Roland Knall from comment #8)
> So I think, support for ssh-agent and pageant (putty's ssh agent) is the
> right way forward.
ssh-agent support is already in place.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Roland Knall changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Roland Knall changed:
What|Removed |Added
Status|VERIFIED|UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Roland Knall changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #8 from Roland Knall ---
Personally I think that, to not store a password in 2016 should be a
no-brainer. It is simply the right thing to do.
That being said, I acknowledge, that many people don't want to
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Graham Bloice changed:
What|Removed |Added
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #6 from Jörg Mayer ---
I personally find the lack to provide a password on the openssh command line
(or at least the config file) to be very patronizing. There are environments
where using key simply isn't an
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Dario Lombardo changed:
What|Removed |Added
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #4 from djcanadianj...@gmail.com ---
even if it had a checkbox to offer to save the password?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #3 from Dario Lombardo ---
This is a bad practice in security. Home made solutions don't fit well. The
solution for ssh authentication without re-enter the password is key or agent.
--
You are receiving
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Stig Bjørlykke changed:
What|Removed |Added
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Dario Lombardo changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
--- Comment #1 from Dario Lombardo ---
It's exactly what expected. A saved password would mean a password on a text
file. A security flaw. If you want to repeatedly capture without enter the
password use the certificates
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012
Alexis La Goutte changed:
What|Removed |Added
CC|
19 matches
Mail list logo