Installing on Centos 7

[nahimov]

Hello! Is it possible to install this package fidogate to centos 7 ?
I'll try to: rpm -i fidogate-5.12-1.x86_64.rpm but have a problem with perl:
error: Failed dependencies:
perl(getopts.pl) is needed by fidogate-5.12-1.x86_64
I have installed perl, but no idea what they want....

[nahimov]

so strange, i install perl-Perl4-CoreLibs, after start rpm -U fidogate-5.12-1.x86_64.rpm, after i see:

Nov 25 18:16:51 v6q2mre27tqvz5i systemd[1]: Unit fidogate.service entered failed state.
Nov 25 18:16:51 v6q2mre27tqvz5i systemd[1]: fidogate.service failed.
Nov 25 18:16:52 v6q2mre27tqvz5i sshd[8705]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.237.131.141 user=root
Nov 25 18:16:54 v6q2mre27tqvz5i sshd[8705]: Failed password for root from 121.237.131.141 port 49183 ssh2
Nov 25 18:16:54 v6q2mre27tqvz5i sshd[8705]: Connection closed by 121.237.131.141 port 49183 [preauth]
Nov 25 18:16:56 v6q2mre27tqvz5i sshd[8713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.237.131.141 user=root
Nov 25 18:16:59 v6q2mre27tqvz5i sshd[8713]: Failed password for root from 121.237.131.141 port 49726 ssh2
Nov 25 18:16:59 v6q2mre27tqvz5i sshd[8713]: Connection closed by 121.237.131.141 port 49726 [preauth]

I'm consufed

[ykaliuta]

I basically abandoned the project since the war in Ukraine started. Historically I used only russian speaking part of fidonet and it mostly supports the war, so I'm not interested in it anymore.

[nahimov]

Hello! What does Fido have to do with war? Fido has always been out of politics. For example, I come from Kyiv, I communicate with you in English, because I don’t know which country you are from and I do not want to violate the opinion of someone. Странно всё это, ну ладно...

[ykaliuta]

The crucial part is that I'm not interested in and I do not use the project anymore. And I explained why. It happens in open source every now and then.

[kosfango]

Nov 25 18:16:51 v6q2mre27tqvz5i systemd[1]: Unit fidogate.service entered failed state.
Nov 25 18:16:51 v6q2mre27tqvz5i systemd[1]: fidogate.service failed.

Did you check fidogate logs? Also you can check:
systemctl status fidogate.service
and
journactl -u fidogate.service

[ykaliuta]

Fidogate itself is not a daemon. systemd unit file is used just to create a directory in /run for flags (it was non-volatile /var/run years ago and a part of the package, but then things changed). I did not check why it does not work anymore or in your case, but it should not be a showstopper, you should be able to create it manually at least.

[kosfango]

Fidogate itself is not a daemon. systemd unit file is used just to create a directory in /run for flags (it was non-volatile /var/run years ago and a part of the package, but then things changes). I did not check why it does not work anymore or in your case, but it should not be a showstopper, you should be able to create it manually at least.

Yes, you are fully right, but systemd unit logs can help to understand the reason of this current issue. As far as I remember, Centos 7 has SELINUX enabled by default and also some debian-based OS have apparmor. Mandatory access control can affect to creating directories needed for Fidogate. Unfortunately, I never tested Fidogate in rmp or deb based OS.

[ykaliuta]

If you know how to fix the unit file I'll apply the patch, no problem

[kosfango]

If you know how to fix the unit file I'll apply the patch, no problem

Let me start my vm ware workstation... As far as I remember, I had Centos7 installed for tests.

[kosfango]

As I wrote before, systemctl logs helped

 fidogate.service - Fidogate runtime prepare
   Loaded: loaded (/usr/lib/systemd/system/fidogate.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2024-01-30 17:34:56 EST; 24s ago
  Process: 14208 ExecStart=/bin/chown ftn:news /run/fidogate (code=exited, status=1/FAILURE)
  Process: 14206 ExecStart=/bin/mkdir -p /run/fidogate (code=exited, status=0/SUCCESS)
 Main PID: 14208 (code=exited, status=1/FAILURE)
Jan 30 17:34:56 localhost.localdomain systemd[1]: Starting Fidogate runtime prepare...
Jan 30 17:34:56 localhost.localdomain chown[14208]: /bin/chown: invalid user: ‘ftn:news’
Jan 30 17:34:56 localhost.localdomain systemd[1]: fidogate.service: main process exited, code=exited, status=1/FAILURE
Jan 30 17:34:56 localhost.localdomain systemd[1]: Failed to start Fidogate runtime prepare.
Jan 30 17:34:56 localhost.localdomain systemd[1]: Unit fidogate.service entered failed state.
Jan 30 17:34:56 localhost.localdomain systemd[1]: fidogate.service failed.
Jan 30 17:30:35 localhost.localdomain sshd[13601]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jan 30 17:31:15 localhost.localdomain polkitd[640]: Registered Authentication Agent for unix-process:14094:25675 (system bus name :1.23
Jan 30 17:31:15 localhost.localdomain systemd[1]: Reloading.
Jan 30 17:31:16 localhost.localdomain polkitd[640]: Unregistered Authentication Agent for unix-process:14094:25675 (system bus name :1.
Jan 30 17:34:50 localhost.localdomain yum[14172]: Installed: perl-Perl4-CoreLibs-0.003-7.el7.noarch
Jan 30 17:34:55 localhost.localdomain groupadd[14193]: group added to /etc/group: name=news, GID=13
Jan 30 17:34:55 localhost.localdomain groupadd[14193]: group added to /etc/gshadow: name=news
Jan 30 17:34:55 localhost.localdomain groupadd[14193]: new group: name=news, GID=13
Jan 30 17:34:55 localhost.localdomain useradd[14198]: new user: name=news, UID=996, GID=13, home=/etc/fidogate, shell=/bin/bash
Jan 30 17:34:56 localhost.localdomain systemd[1]: Starting Fidogate runtime prepare...
-- Subject: Unit fidogate.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fidogate.service has begun starting up.
Jan 30 17:34:56 localhost.localdomain chown[14208]: /bin/chown: invalid user: ‘ftn:news’
Jan 30 17:34:56 localhost.localdomain systemd[1]: fidogate.service: main process exited, code=exited, status=1/FAILURE
Jan 30 17:34:56 localhost.localdomain systemd[1]: Failed to start Fidogate runtime prepare.
-- Subject: Unit fidogate.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Looks like issue around:

fidogate/debian/fidogate.service

Lines 6 to 8 in e4e8b94

	ExecStart=/bin/mkdir -p /run/fidogate
	ExecStart=/bin/chown ftn:news /run/fidogate
	ExecStart=/bin/chmod 770 /run/fidogate

but seems it's for debian.

Into spec file:

fidogate/packages/rpm/fidogate.spec.in

Line 18 in e4e8b94

%define user news

Also:

fidogate/src/Makefile.am

Lines 127 to 130 in e4e8b94

	chown news $(DESTDIR)$(libexecdir)/send-fidogate; \
	echo " chown news $(DESTDIR)$(libexecdir)/send-fidogate"; \
	chown news $(DESTDIR)$(libexecdir)/xct; \
	echo " chown news $(DESTDIR)$(libexecdir)/xct"; \

Also:

fidogate/Makefile.am

Lines 56 to 60 in e4e8b94

	for d in $(FDESTDIR); do \
	chown ${OWNER}:${GROUP} $(DESTDIR)$$d || exit 1; \
	echo "chown ${OWNER}:${GROUP} $(DESTDIR)$$d"; \
	done; \
	else echo "Cannot change owner to ${OWNER}:${GROUP}"; \

I think it should be news:news, but I don't understand where rpm get ftn:new

[kosfango]

If you know how to fix the unit file I'll apply the patch, no problem

Yes, found:

fidogate/packages/rpm/fidogate.spec.in

Line 56 in e4e8b94

install -D -m 0644 debian/%{name}.service \

[ykaliuta]

Yes, I create user ftn in debian postinst and probably forgot it in %postin

[kosfango]

Yes, I create user ftn in debian postinst and probably forgot it in %postin

The issue is a simple, but need to think how it should be most correctly:
there we have ftn:ftn

fidogate/debian/fidogate.postinst

Lines 37 to 38 in e4e8b94

	chown -R ftn:ftn /etc/$PACKAGE
	chown ftn:ftn /var/lock/$PACKAGE/ \

there we have ftn:news

fidogate/debian/fidogate.service

Line 7 in e4e8b94

ExecStart=/bin/chown ftn:news /run/fidogate

there ftn:news

fidogate/debian/fidogate.postinst

Line 41 in e4e8b94

chown -R ftn:ftn /var/spool/$PACKAGE/ /var/lib/$PACKAGE

and etc:

fidogate/debian/fidogate.postinst

Lines 43 to 44 in e4e8b94

	chown news:ftn /usr/bin/ngoper
	chown ftn:news /usr/lib/$PACKAGE/rfc2ftn

[ykaliuta]

Yes, it's on purpose. To marry news and ftn. And there are SUID binaries for that.

[kosfango]

Perhaps, we should create additional user around here:

fidogate/packages/rpm/fidogate.spec.in

Lines 62 to 63 in e4e8b94

	useradd -r -g news -d /etc/%{name} -c "Fidonet user" %{user}

but I dont know if it's a good solution:
something like:

useradd -r -g news -d /home/ftn -c "Fidogate user" ftn

However, it looks like a bad hardcode