Perl 6 binding to crypt(3) on Unix-like systems
Switch branches/tags
Latest commit 8147221 Apr 22, 2017 @jonathanstowe Fix licence
Failed to load latest commit information.
lib/Crypt Remove version literal Mar 12, 2016
t done -> done-testing Sep 4, 2015
.gitignore Add precomp stuff Dec 24, 2015
.travis.yml Add .travis.yml May 6, 2015 Make zef compatible Jan 24, 2017
LICENCE rename LICENCE as en_GB May 30, 2016
META6.json Fix licence Apr 22, 2017 Update README Jan 21, 2017


Provide a simple Perl 6 binding to POSIX crypt(3) function


This is a binding to the crypt() function that is typically defined in libcrypt on most Unix-like systems or those providing a POSIX API.

There is a single exported subroutine crypt() that perform a one-way encryption of the supplied plain text, with the provided "salt". Depending on the implementation on your system, the structure of the salt may influence the algorithm that is used to perform the encryption. The default will probably be the DES algorithm that was traditionally used to encrypt passwords on a Unix system.

Because this is intended primarily for the encryption of passwords and is "one way" (i.e. there is no mechanism to "decrypt" the crypt text,) it is not suitable for general purpose encryption.

In order to check whether a password entered by a user is correct it should be encrypted using the stored encrypted password as the "salt" - the result will be the same as the stored crypt text if the password is the same.


Currently there is no dedicated test to determine whether your platform is supported, the unit tests may simply fail horribly.

Assuming you have a working perl6 installation you should be able to install this with panda :

# From the source directory

panda install .

# Remote installation

panda install Crypt::Libcrypt

This should work equally well with zef but I haven't tested it.


Suggestions/patches are welcomed via github at:

I'm not able to test on a wide variety of platforms so any help there would be appreciated. Also help with the documentation of which platforms support which encryption algorithms is probably required.


This is free software.

Please see the LICENCE file in the distribution

© Jonathan Stowe 2015, 2016, 2017