Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 May 2015 17:21:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 200444] security/trousers: weird rcorder, bad nodes, possible loop
Message-ID:  <bug-200444-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200444

            Bug ID: 200444
           Summary: security/trousers: weird rcorder, bad nodes, possible
                    loop
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: hrs@FreeBSD.org
          Reporter: c.kworr@gmail.com
             Flags: maintainer-feedback?(hrs@FreeBSD.org)
          Assignee: hrs@FreeBSD.org

Created attachment 157131
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=157131&action=edit
PS: Adding a script to graphviz all the rcorder, helps to see the big picture.

Hi all.

1. 'tcsd' service mentions a few absent services: 'tmpd' and 'kerberos'. Dunno
about 'tpmd', if it depends on trousers maybe it should mentions 'tcsd'
instead?

2. 'tcsd' wants to start after 'SERVERS' which as per rcorder happens after
'kdc' and that's actually Kerberos provider. This way 'tcsd' can't be started
before 'kerberos' as it depends on it.

3. 'tcsd' wants to start before 'named' thus pushing 'named' further down the
tree. Resolver is a vital service and shouldn't be pushed like that, some other
services can fail if resolver is not started yet. This is not a prolem per se
unless 'tcsd' would introduce more rcorder weirdness. And rcorder works
regardless whether service is disabled or enabled, this means even that I need
to install trousers only to make remmina or xfce4 work the bugs are just
jumping in.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200444-13>