search

ceremcem / unlock-luks-partition

Unlock a LUKS partition via SSH
40 stars 3 forks source link

Strict host key checking must be disabled #4

Closed ceremcem closed 2 years ago

ceremcem commented 5 years ago

To enable a second step flexibility, strict host key checking must be disabled so that the target node will be able to connect to another (possibly an untrusted) server which will forward the connections to our server.

Since the server already has its encryption layer, there is no possible vulnerability introduced.

ceremcem commented 5 years ago

Already disabled with -y -y option.

ralienpp commented 2 years ago

@ceremcem, what is the role of duplicating the -y parameter? The documentation for https://linux.die.net/man/1/dbclient doesn't mention any effects for this case. Is this written twice on purpose?

ceremcem commented 2 years ago

This can't be a typo, I think I added -y twice on purpose. However you are also right. I can neither remember nor find again why I might have added this switch twice.

This issue can be closed after verifying that the single -y switch works as expected.

ralienpp commented 2 years ago

It works with a single -y (tested on 2 Debian 11 systems).

ceremcem commented 2 years ago

Thanks for testing. I'd accept the PR for this if you open one.

On Tue, Feb 22, 2022, 11:41 Alex Railean @.***> wrote:

It works with a single -y (tested on 2 Debian 11 systems).

— Reply to this email directly, view it on GitHub https://github.com/ceremcem/unlock-luks-partition/issues/4#issuecomment-1047551185, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSVCAWP2TGZIH43C22ZHUTU4NDZ3ANCNFSM4FNU755Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you modified the open/close state.Message ID: @.***>