Linux - Security This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
04-28-2009, 03:58 PM
|
#1
|
Senior Member
Registered: Jul 2003
Location: Toronto, Ontario, Canada
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,573
|
Tiger warnings about avahi-daemon - should I be concerned?
I installed Tiger onto my Lenny box, and it gives me the following warnings repeatedly:
"The process `avahi-daemon' is listening on socket 52636" (or other numbers)
"The process `rpc.statd' is listening on socket 34157" (or other numbers)
Should I be concerned? Is it time to declare my computer a security risk and detonate it with dynamite immediately?
|
|
|
04-28-2009, 04:54 PM
|
#2
|
LQ Guru
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870
|
Quote:
Originally Posted by mark_alfred
I installed Tiger onto my Lenny box, and it gives me the following warnings repeatedly:
"The process `avahi-daemon' is listening on socket 52636" (or other numbers)
"The process `rpc.statd' is listening on socket 34157" (or other numbers)
Should I be concerned? Is it time to declare my computer a security risk and detonate it with dynamite immediately?
|
I would suggest you instead determine whether you need/want Avahi and/or RPC. If you don't, then you can always remove them (no high explosives necessary). I think the Avahi package is called avahi-daemon and RPC is provided by portmap, which is a dependency of both NFS and NIS.
Last edited by win32sux; 04-28-2009 at 05:01 PM.
|
|
|
04-28-2009, 11:59 PM
|
#3
|
Senior Member
Registered: Jul 2003
Location: Toronto, Ontario, Canada
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,573
Original Poster
|
Is Tiger just anally-retentive?
Quote:
Originally Posted by win32sux
I would suggest you instead determine whether you need/want Avahi and/or RPC. If you don't, then you can always remove them (no high explosives necessary). I think the Avahi package is called avahi-daemon and RPC is provided by portmap, which is a dependency of both NFS and NIS.
|
I think libsane depends on avahi, and I've a scanner. I may get rid of portmap, but I'm worried that mount indirectly relies upon it.
Anyway, from what I understand, these are not unusual programs. Why is Tiger making a fuss over them?
|
|
|
04-29-2009, 04:15 AM
|
#4
|
Moderator
Registered: May 2001
Posts: 29,415
|
It's just objectively listing what's going on. Determining something to be benign or malicious is left to human interpretation.
|
|
|
04-29-2009, 07:45 AM
|
#5
|
LQ Guru
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870
|
Quote:
Originally Posted by mark_alfred
I think libsane depends on avahi, and I've a scanner.
|
It depends on the library, not the daemon (look here).
Quote:
I may get rid of portmap, but I'm worried that mount indirectly relies upon it.
|
Unless you've got clients that make use of that service, you don't need it. If you don't want to remove the package, keep in mind you could instead just make it so that it doesn't get automatically loaded at startup time (the same could be said for the Avahi daemon).
Last edited by win32sux; 04-29-2009 at 08:32 AM.
|
|
|
04-30-2009, 12:20 PM
|
#6
|
Senior Member
Registered: Jul 2003
Location: Toronto, Ontario, Canada
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,573
Original Poster
|
unSpawn: Objectively? It seems that flagging something with a big all-capitals "WARN" is hardly objective. Plus, it's not listing all processes; rather, it's being selective in that which it warns about. Granted, though, it did not accord the status of "FAIL" to the aforementioned processes, so perhaps they're not something that need raise too much concern.
win32sux: when in doubt, throw it out. Be free of unnecessary clutter. So, gone are portmap and avahi-daemon, along with a few others. Time to reboot and see if the machine has survived this surgery.
[later] Well, the reboot was a success. It'll be interesting to discover if I've lost any functionality from the recent removals.
Last edited by mark_alfred; 04-30-2009 at 12:36 PM.
|
|
|
All times are GMT -5. The time now is 11:52 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|