Bug 1564273 - gnome-session listens on tcp ports in default configuration
Summary: gnome-session listens on tcp ports in default configuration
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: 28
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-05 21:21 UTC by pav
Modified: 2018-04-15 23:21 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-15 23:21:06 UTC
Type: Bug

Attachments (Terms of Use)

Description pav 2018-04-05 21:21:54 UTC
Description of problem:

Upgraded to Fedora 28 beta, and noticed gnome-session listens on tcp ports on all interfaces:

# netstat -tap|grep gnome-session
tcp        0      0 *               LISTEN      1367/gnome-session- 
tcp        0      0 *               LISTEN      2088/gnome-session- 
tcp6       4      0 [::]:33431              [::]:*                  LISTEN      2088/gnome-session- 
tcp6       0      0 [::]:33435              [::]:*                  LISTEN      1367/gnome-session- 

One of the above processes is gdm gnome-session, the other user gnome-session.

It's unclear to me why it listens on tcp for external interfaces at all.
It did not do so in Fedora 27 before upgrade.

Version-Release number of selected component (if applicable):
Fedora 28 Beta

How reproducible:
Didn't try multiple installations, but would guess reproducible in default configuration.

Steps to Reproduce:
1. Upgrade to Fedora 28 from Fedora 27 with dnf system-upgrade. (Maybe also for clean reinstall?)
2. Log in
3. Check netstat -tap

Actual results:
gnome-session listens on tcp ports.

Expected results:
I would expect gnome-session doesn't listen on any tcp ports, which was the situation in Fedora 27.

Comment 1 pav 2018-04-15 23:21:06 UTC
Upgrade to gnome-session-3.28.1-1.fc28 fixed this.

Note You need to log in before you can comment on or make changes to this bug.