Re: [Open-scap] removing telnet client breaks fence agents

On 11/1/19 1:29 PM, Gabe Alford wrote: On Fri, Nov 1, 2019 at 10:46 AM Trevor Vaughan > wrote: I don't see a reason to remove the rule in general but: 1) Having the telnet *client* present isn't really a big deal if you have pretty much any

Re: [Open-scap] removing telnet client breaks fence agents

On Fri, Nov 1, 2019 at 10:46 AM Trevor Vaughan wrote: > I don't see a reason to remove the rule in general but: > > 1) Having the telnet *client* present isn't really a big deal if you have > pretty much any scripting language, or modern SSH that allows the NULL > cipher > IIRC as of one of the

Re: [Open-scap] removing telnet client breaks fence agents

I don't see a reason to remove the rule in general but: 1) Having the telnet *client* present isn't really a big deal if you have pretty much any scripting language, or modern SSH that allows the NULL cipher 2) All rules are 'unless you need them' at which point you can tailor them out of your

Re: [Open-scap] removing telnet client breaks fence agents

adding SSG list. Dne 01. 11. 19 v 11:30 Vojtech Polasek napsal(a): Hello all, I am fixing the following bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1729222 Brief summary: as part of several profiles, in this case NCP profile in rhel7, we are removing the telnet package containing

[Open-scap] removing telnet client breaks fence agents

Hello all, I am fixing the following bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1729222 Brief summary: as part of several profiles, in this case NCP profile in rhel7, we are removing the telnet package containing the Telnet client. But this removal of telnet package causes