| Summary: | Prevent ~/.ssh creation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | alexandreprovencio | ||||
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED FIXED | ||||||
| Severity: | enhancement | CC: | alexandreprovencio, djm, dtucker | ||||
| Priority: | P5 | ||||||
| Version: | 8.2p1 | ||||||
| Hardware: | amd64 | ||||||
| OS: | Linux | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 3162 | ||||||
| Attachments: |
|
||||||
|
Description
alexandreprovencio
2020-04-30 05:56:44 AEST
There is no way at present. Since ssh assumes pretty deeply that ~/.ssh exists, to implement this properly would require that ssh search its configuration for anything that may write to that directory before it stopped doing so. (In reply to Damien Miller from comment #1) > There is no way at present. Since ssh assumes pretty deeply that > ~/.ssh exists Most of the uses I can think of are on the server side, and most of those (and the client for that matter) are read-only. I'll try moving it and see what breaks. Created attachment 3402 [details]
create ~/.ssh on demand
~/.ssh/known_hosts is the only thing I could find.
ssh-keygen does its own thing which looks more or less ok.
The patch has been applied and will be in the next major release. Thanks for the report. That's great! Thank you lots for your time :) Mass close of all bugs fixed in 8.4 release. |