Displaying 6 results from an estimated 6 matches for "manon".
Did you mean:
anon
2016 Dec 28
2
certificates keys on pkcs11 devices
...dd.c line 580
if (pkcs11provider != NULL) {
if (update_card(agent_fd, !deleting, pkcs11provider) == -1)
ret = 1;
goto done;
}
does not check for additional (certifcate)-files files on the command line
and update_card neither does.
Is there any intention to change this?
Thanks in alot,
Manon
2024 Jul 03
4
Request for a Lockdown option
...ed in parallel or be handed out to different Users or for Key Rotarian.
I believe that this could be helpful in situation where Port-knocking is used today and this could give Administrators some workaround when there are problems with ssh and sshd.
How do you like this idea?
Kind Regards,
Manon
2024 Jul 03
2
Request for a Lockdown option
Manon,
On Thu, 4 Jul 2024 at 05:00, Manon Goo <manon.goo at dg-i.net> wrote:
> My Idea would be to have a shared secret option that the client and server would have to proof to know when initiating the Handshake. The Server or client could terminate the connection immediately when the peer d...
2024 Jul 03
1
Request for a Lockdown option
...m, then your solution may not be helpful because SSH is still exposed and attackable.
The solution I do propose is an alterative to Port-Knocking or packet filtering because it aims to un-expose the vulnerability of ssh and give the Administrators some time to fix the problems.
Kind Regards
Manon
2017 Aug 01
0
Incompatibility Windows 7
...some point there
>>>> will be some windows update that will break compatibility. I had
>>>> Samba 3.6.x running last year and I couldn't keep it working anymore.
>>>>
>>>>
>>>>
>>>>
>>>> On 07/21/17 08:32, Manon JEANJEAN via samba wrote:
>>>>> Hello again,
>>>>>
>>>>> False Server max protocol = NT1 doesn't work because all my server
>>>>> fell there are 20 minutes.
>>>>> So it's necessary to find a new idea.
>>>&g...
2024 Jul 04
1
Request for a Lockdown option
On 04.07.24 01:41, Manon Goo wrote:
> - some users private keys are lost
Then you go and remove the corresponding pubkeys from wherever they're
configured.
Seriously, even if you do not scan which pubkey is configured where
*now* (as is part of our usual monitoring), it'll be your "number <3"...