Hi,

I really suggest you ask these questions in a place that's in your
primary language because I don't think we are going to be able to
effectively communicate.

On Tue, Jul 14, 2026 at 01:16:22AM +0200, jean-christophe wrote:
> On mar., 2026-07-14 at 01:00 +0200, jean-christophe wrote:
> > https://paste.debian.net/hidden/5e9fade2

No such paste.

> > i will be trying to secure my master client and clean it.

What's a "master client"?

What do you mean by "secure" and "clean"? Those words mean a lot of
different things to different people.

> > i have some warning like /usr/bin/sshd and others

Please post exact messages not what you think they are "like". We cannot
read your mind. Say what you did, what exactly happened and what you
think should have happened.

> > could you help me please,

Almost certainly not given the lack of detail in your emails.

> /usr/sbin/sshd                                           [ Warning ]
> /usr/bin/curl                                            [ Warning ]
> /usr/bin/GET                                             [ Warning ]
> /usr/bin/locate                                          [ Warning ]
> /usr/bin/locate.findutils                                [ Warning ]
> /usr/bin/lwp-request                                     [ Warning ]

What command produced the above output?

> i suspect a attacker, but i am not sure but may be there are a
> backdoors

A misunderstanding is far more likely.

> Checking /dev for suspicious file types                  [ Warning ]
> Checking for hidden files and directories                [ Warning ]
> 
> if you are a correct howto solve this warning and securing my client

Without knowing what tool produced that output we have no way of
guessing what it is warning about. I am sure you could read its
documentation and find out how to show what it is warning about. That
would be useful for us as we try to help.

Again, a support venue that's in your language may be easier,

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Reply via email to