App-DocKnot
view release on metacpan or search on metacpan
t/data/generate/remctl/docknot.yaml view on Meta::CPAN
The remctld server requires libevent 1.4.x or later. It's only been
tested with libevent 1.4.13-stable and later, but should work with 1.4.4
or later. It is now only tested with libevent 2.x, so moving to a later
version of libevent if possible is recommended.
The remctl server will support regex ACLs if the system supports the POSIX
regex API. The remctl server also optionally supports PCRE regular
expressions in ACLs. To include that support, the PCRE library is
required.
To build the remctl client for Windows, the Microsoft Windows SDK for
Windows Vista and the MIT Kerberos for Windows SDK are required, along
with a Microsoft Windows build environment (probably Visual Studio).
remctl has only been tested with the 3.2.1 MIT Kerberos for Windows SDK.
To run the resulting binary, MIT Kerberos for Windows must be installed
and configured. The client was tested on Windows XP and Vista and should
work on Windows 2000 and up; however, the primary maintainer does not use
or test Windows, so it's always possible Windows support has broken. The
server is not supported on Windows.
To build the Perl bindings for the C client library, you will need Perl
5.8 or later.
To build the PHP bindings for the C client library, you will need PHP 5.x
or later and phpize, plus any other programs that phpize requires. PHP
5.x support has only been tested on 5.2 and 5.3, and PHP support is now
only tested on PHP 7.x and later.
To build the Python bindings for the C client library, you will need
Python 2.3 or later (primarily tested with Python 2.7). Python 3 is not
(yet) supported.
To build the Ruby bindings for the C client library, you will need Ruby
1.8 or later (primarily tested with 2.5 and later).
None of the language bindings have been tested on Windows.
A Java client and Java server are available in the java subdirectory, but
they are not integrated into the normal build or built by default. There
is a basic Makefile in that directory that may require some tweaking. It
currently requires the Sun Java JDK (1.4.2, 5, or 6) or OpenJDK 6 or
later. A considerably better Java client implementation is available on
the `java` branch in the Git repository but has not yet been merged.
test:
lancaster: true
prefix: |
remctl comes with a comprehensive test suite, but it requires some
configuration in order to test anything other than low-level utility
functions. For the full test suite, you will need to have a keytab that
can authenticate to a running KDC. Using a test KDC environment, if you
have one, is recommended.
Follow the instructions in `tests/config/README` to configure the test
suite.
Now, you can run the test suite with:
suffix: |
On particularly slow or loaded systems, you may see intermittent failures
from the `server/streaming` test because it's timing-sensitive.
The test suite will also need to be able to bind to 127.0.0.1 on port
11119 and 14373 to run test network server programs.
To test anonymous authentication, the KDC configured in the test suite
needs to support service tickets for the anonymous identity (not a
standard configuration). This test will be skipped if the KDC does not
support this.
To test user handling in remctld, you will need the `fakeroot` command
(available in the `fakeroot` package in Debian and Ubuntu). This test
will be skipped if `fakeroot` isn't available.
The following additional Perl modules will be used by the test suite for
the main package and the Perl bindings if installed:
* Test::MinimumVersion
* Test::Perl::Critic
* Test::Pod
* Test::Spelling
* Test::Strict
* Test::Synopsis
All are available on CPAN. Those tests will be skipped if the modules are
not available.
( run in 0.502 second using v1.01-cache-2.11-cpan-140bd7fdf52 )