Hello Jerome,
> You are right.
> Meanwhile I added an entry in my TODO list concerning this package.
> I also noticed that there is two flag-file on my box: I would say that one is
> enough,
> but I cannot say more right now because I am not familiar with this part of
> the code.
> (In the past,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Giueppe,
On 24/06/16 19:50, Giuseppe Bilotta wrote:
> Hello Jerome,
>
> On Fri, Jun 24, 2016 at 4:43 PM, Jerome BENOIT wrote:
>> On 24/06/16 15:21, Giuseppe Bilotta wrote:
>>> So the problem is that one of the leftover files prevented the ag
Hello Jerome,
On Fri, Jun 24, 2016 at 4:43 PM, Jerome BENOIT wrote:
> On 24/06/16 15:21, Giuseppe Bilotta wrote:
>> So the problem is that one of the leftover files prevented the agent
>> from starting.
>
> This is not a problem, this mechanism is meant to allow several sessions
> to use the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Again,
On 24/06/16 15:21, Giuseppe Bilotta wrote:
> OK, I think I found a solution!
Glad to hear.
>
> When I checked the permissions of my .ssh folder and all the files
> within, I noticed there were a lot of leftover agent-* files in it. I
>
OK, I think I found a solution!
When I checked the permissions of my .ssh folder and all the files
within, I noticed there were a lot of leftover agent-* files in it. I
killed my manually-started ssh-agent session, removed all the leftover
files, logged out, and now the agent starts correctly when
Hello Jerome,
>> I'm using ssh 1:7.2p2-5
>
> Now I am also using ssh 1:7.2p2-5 , but I cannot still reproduce the issue.
8-/
> I suspect a bad interference with some pam_module present on your box but
> absent on mine
> and/or a privilege issue.
I will try disabling some of the less used modul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Giuseppe, thanks for your feed back.
On 24/06/16 09:07, Giuseppe Bilotta wrote:
> Hello,
>>
>> My understanding is that you have only one key, the traditional rsa key.
>
> This is indeed the case.
ok
>
>> I have tried to reproduce your issue
Hello,
>
> My understanding is that you have only one key, the traditional rsa key.
This is indeed the case.
> I have tried to reproduce your issue with a fake user on my box: it works
> here.
> Have you tried to start an ssh-agent by hand ?
Starting ssh-agent by hand with
eval $(ssh-agent)
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello.
On 23/06/16 15:19, Giuseppe Bilotta wrote:
> Hello again,>> Is there anything I can do to debug the issue and
> provide more information?
>>
>> Can you check that your current set is conform to pam_ssh(8) ?
>
> I have not altered the pam con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks for the log. Please give me some time to scrutinize it.
Thanks, Jerome
On 23/06/16 15:19, Giuseppe Bilotta wrote:
> Hello again,>> Is there anything I can do to debug the issue and
> provide more information?
>>
>> Can you check that your cur
Hello again,>> Is there anything I can do to debug the issue and
provide more information?
>
> Can you check that your current set is conform to pam_ssh(8) ?
I have not altered the pam configuration myself until now, so the
configuration is the one enabled by the package directly. greppng for
ssh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Again:
On 23/06/16 14:37, Giuseppe Bilotta wrote:
> Hello Jerome,
>
> thanks for your time
>
>>> Not much to say: as per the title, I just found out that the latest
>>> version of libpam-ssh does not launch an ssh-agent,
>>
>> It does on my box
Hello Jerome,
thanks for your time
>> Not much to say: as per the title, I just found out that the latest
>> version of libpam-ssh does not launch an ssh-agent,
>
> It does on my box.
Is there anything I can do to debug the issue and provide more information?
>> even though the
>> password does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Giusepp, thanks a lot for your report.
On 23/06/16 09:46, Giuseppe Bilotta wrote:
> Package: libpam-ssh
> Version: 2.1+ds1-1
> Severity: important
>
> Not much to say: as per the title, I just found out that the latest
> version of libpam-ssh
Package: libpam-ssh
Version: 2.1+ds1-1
Severity: important
Not much to say: as per the title, I just found out that the latest
version of libpam-ssh does not launch an ssh-agent, even though the
password does unlock at least one of the user keys. This is both for
local and remote logins.
-- Syste
15 matches
Mail list logo
