krb5 port: -current behaves differently than 4.X w.r.t rsh (possibly EPERM from bind)

[Tillman Hodgson]

Howdy folks,

I'm this on trying on -current to see if I can work with someone here to
get this problem trouble-shot and fixed.

There was a brief follow-up on the ports mailing list (viewable at
http://groups.google.ca/groups?hl=en&lr=&selm=1102037006.00184340.1102024801%4010.7.7.3)
describing how 5.3 and 6.0 bind in kcmd returns EPERM in spite of there
being no firewall in place.

-T


-- 
"Humanity has advanced, when it has advanced, not because it has been
 sober, responsible, and cautious, but because it has been playful,
 rebellious, and immature."
    -- Tom Robbins (1936 - )
-------------- next part --------------
An embedded message was scrubbed...
From: Tillman Hodgson <tillman at seekingfire.com>
Subject: krb5 port: -current behaves differently than 4.X w.r.t rsh
Date: Tue, 23 Nov 2004 16:00:09 -0600
Size: 3779
Url: http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041214/60e97dd7/attachment.mht