view release on metacpan or  search on metacpan

t/data/update/remctl/docknot.yaml  view on Meta::CPAN

  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.
sections:
- body: |
    (These instructions are not tested by the author and are now dated.
    Updated instructions via a pull request, issue, or email are very
    welcome.)

    First, install the Microsoft Windows SDK for Windows Vista if you have not
    already.  This is a free download from Microsoft for users of "Genuine
    Microsoft Windows."  The `vcvars32.bat` environment provided by Visual
    Studio may work as an alternative, but has not been tested.

    Next, install the [MIT Kerberos for Windows
    SDK](https://web.mit.edu/kerberos/www/dist/index.html).  remctl has been
    tested with version 3.2.1 but should hopefully work with later versions.

    Then, follow these steps:

    1. Run the `InitEnv.cmd` script included with the Windows SDK with
       parameters `"/xp /release"`.

    2. Run the `configure.bat` script, giving it as an argument the location
       of the Kerberos for Windows SDK.  For example, if you installed the KfW
       SDK in `"c:\KfW SDK"`, you should run:

       ```
           configure "c:\KfW SDK"
       ```

    3. Run `nmake` to start compiling.  You can ignore the warnings.

    If all goes well, you will have `remctl.exe` and `remctl.dll`.  The latter
    is a shared library used by the client program.  It exports the same
    interface as the UNIX libremctl library.
  title: Building on Windows
support:
  email: eagle@eyrie.org
  github: rra/remctl
  web: https://www.eyrie.org/~eagle/software/remctl/
synopsis: remote authenticated command execution with ACLs
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.
vcs:
  browse: https://git.eyrie.org/?p=kerberos/remctl.git
  github: rra/remctl
  openhub: https://www.openhub.net/p/remctl
  status:
    travis: rra/remctl
  type: Git
  url: https://git.eyrie.org/git/kerberos/remctl.git
version: '3.15'