Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E. R." Newsgroups: comp.os.linux.misc Subject: Re: Is It Time To Replace SSH ??? Date: Mon, 19 Dec 2022 12:27:25 +0100 Lines: 23 Message-ID: References: <87r0x0xmre.fsf@usenet.ankman.de> <6sScnWpDiqXc7QD-nZ2dnZfqnPGdnZ2d@earthlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net 3yo0y3aWkz+F2bArnbuilg9K8sq892Px26QmNY1OWpB6+t7ZwG Cancel-Lock: sha1:f+MEZzI7Gx4n552ebMKLobZfvt0= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Content-Language: es-ES, en-CA In-Reply-To: Xref: csiph.com comp.os.linux.misc:36565 On 19/12/2022 03.08, 26C.Z969 wrote: > On 12/18/22 8:21 AM, Marc Haber wrote: >> "Carlos E. R." wrote: >>> Monitoring logs is a kludge. >> >> Right, ssh and services should have hooks for that. Sadly, for ssh, >> this is regularly bludgeoned down by upstream if requested. > >   Ah, so you DO see a little of what I'm talking about ... > >   And "hooks" are a kludge in and of themselves ... how >   about building what those hooks do INTO the SSH app >   in the first place, integrated ? Because that adds bloat, and makes sshd more difficult to analyze and maintain. More failure points. Keep to the unix principle of small programs tht do some task well. -- Cheers, Carlos E.R.