Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
not a suse person, but I'd do it at the command line. Open a terminal window, type "su -" to switch to root, then type "passwd" it will prompt you for a new password, and confirm it etc... What Desktop Manager are you running, that would help me help you do it through the GUI.
I think that I have been hacked because when I started my computer today I saw a login for the AVG user. When I saw this I went to the control center and erased it. Is this enough to kick him/her off my computer?
Erasing an account will make it impossible for someone to gain access through that 'hole', but not impossible if other holes exists.
Besides, by erasing the account you'll disown processes and files which ain't good.
If you mean AVG as in "Anti-Virus Software by Grisoft", did you install their software? If not please:
- reset the shell to /bin/false, /sbin/nologin or whatever inert dummy shell you have
and check your:
- processes for processes owned by that user,
- filesystem for files owned by that user,
- login records (last, lastb, faillog) and system, application and firewall logs for any unusual activity.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.