Bug 1213128 - wrong user tcpcrypt
Summary: wrong user tcpcrypt
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: tcpcrypt
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1312703
TreeView+ depends on / blocked
 
Reported: 2015-04-19 06:58 UTC by Jean-Jacques Sarton
Modified: 2017-08-08 11:56 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-08 11:56:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-Jacques Sarton 2015-04-19 06:58:04 UTC
Description of problem:

tcpcryptd fail to start, user tcpcryptd is not found. 
A look in /etc/passwd show that the user created is tcpcrypt instead of tcpcryptd.


Version-Release number of selected component (if applicable):
tcpcrypt-0.4-0.3.bb990b1b.fc21.x86_64

How reproducible:
always

Steps to Reproduce:
1. install tcpcrypt, start tcpcryptd and look at the status reported by systemctl status. (tcpcryptd: Can't find user 'tcpcryptd')

2. systemctl start tcpcryptd

3.systemctl status tcpcryptd

Actual results:
tcpcryptd fail to start

Expected results:
tcpcryptd working

Additional info:

Comment 1 Fedora End Of Life 2015-11-04 12:37:19 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Jan Kurik 2015-12-02 19:24:29 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Jan Kurik 2016-02-24 13:23:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 4 Edward O'Callaghan 2016-02-29 00:45:39 UTC
Hi,

This issue also exists in Fedora 23 (stable) as you might imagine.

Any news on getting this fixed, seems like some minor adjustments to the spec file and a rebuild is all that is needed?

Kind Regards,
Edward.

Comment 5 Edward O'Callaghan 2016-02-29 01:11:08 UTC
Actually turns out that,

$ sudo grep tcpcryptd /etc/passwd
tcpcrypt:x:983:974:tcpcrypt daemon account:/var/run/tcpcryptd:/sbin/nologin

Thus the issue is perhaps more likely to do with:

https://bugzilla.redhat.com/show_bug.cgi?id=1312703

Sorry for the noise but that is a bit of extra information.
Cheers,
Edward.

Comment 6 Edward O'Callaghan 2016-02-29 04:00:03 UTC
Ah, so the issue here is a minor typo in the RPM spec file:

- 
tcpcrypt:x:983:974:tcpcrypt daemon account:/var/run/tcpcryptd:/sbin/nologin

+ 
tcpcryptd:x:983:974:tcpcrypt daemon account:/var/run/tcpcryptd:/sbin/nologin


That works around that issue.

Comment 7 Paul Wouters 2016-04-08 13:16:59 UTC
Fixing that actually just causes it to crash. I met with the tcpcrypt people yesterday and the will give me some updates on the unit file to fix things. Expect a new package in the next couple of days.

Comment 8 Fedora End Of Life 2017-07-25 18:53:55 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2017-08-08 11:56:53 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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