Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have fedora 23 as my desktop and I want make sure if any one has intruded in the past two weeks. Searching the web, I understood that for any possible ssh login, I have to check
Quote:
/var/log/secure
But this file does not exist.
Any suggestions to find out about possible sneaking with the help of the command line is very appreciated.
Honestly, I'm not lazy...
I was hoping to be able to grep the date in journaltcl and check to see anything creepy, but seems that the date does not lead me to what I should look for.
"Vague oddities," like "weird mouse movement" (especially ...), and "occasional slow-downs," are really not cause for suspicion that "someone, somewhere, somehow," has broken into your system and is right there, right now, creating mischief.
Sometimes, a substantial slowdown can be generated by something as innocuous as a file-content indexing daemon. The process runs infrequently but generates a lot of I/O activity when it does. Competition for the drive causes other processes to slow down.
You should, of course, know by what means your systems might be accessible to the outside world, what credentials are needed and so-forth. You should also always be keeping the software up-to-date. You should know that no services are running (nor listed in "xinetd") other than those which you know and intend to be running. And, so on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.