https://bugzilla.mindrot.org/show_bug.cgi?id=3706
--- Comment #1 from Dominique Martinet <[email protected]> --- Replying to myself for the first point: > Can you think of a way to do handle just exactly +1 version upgrade (9.7p1 -> > 9.8p1) more smoothly I looked a bit more and rather than just the path change the problem would be this protocol change: /* * Protocol from reexec master to child: * string configuration + * uint64 timing_secret + * string host_keys[] { + * string private_key + * string public_key + * string certificate + * } * string included_files[] { * string selector * string filename so I don't see any remotely clean way of doing that for this particular update. Unless there's a great idea somewhere, let's focus this bz about further updates -- it doesn't make sense to freeze this protocol in my opinion but perhaps add a version field first the next time there's a breakage, so at least n->n+1 might be handled. Thanks -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
