| Summary: | "SetupCommand" invoked before connecting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Helmut Grohne <helmut> | ||||
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED WONTFIX | ||||||
| Severity: | enhancement | CC: | djm, dkg, helmut, markus | ||||
| Priority: | P2 | ||||||
| Version: | 5.6p1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
|
Description
Helmut Grohne
2010-08-24 07:16:31 AEST
I'd be interested in this, but i'm more interested in the proposed KnownHostsCommand option (#1777), specifically for host key management. One could use the proposed SetupCommand for host key management, but only by manually tweaking the known hosts file itself (which might not be at a known location unless the child processes get passed the full ssh config (see #1766) (In reply to comment #0) > Solutions: > ~~~~~~~~~~ > 1) (Ab)using ProxyCommand. This is employed in some howtos on port > knocking. It however has the disadvantage that TCPKeepAlive and some > timeout options are no longer honoured. I don't see how using proxy command for port knocking is an abuse as TCP keep alives are usually useless. We really don't want to add another *Command for connection setup; ProxyCommand seems completely sufficient. closing resolved bugs as of 8.6p1 release |