Bug 196656 - New port: security/hs-pam
Summary: New port: security/hs-pam
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-haskell (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-12 20:42 UTC by martin
Modified: 2015-01-19 18:46 UTC (History)
1 user (show)

See Also:


Attachments
port directory contents: security/hs-pam (1.41 KB, text/plain)
2015-01-12 20:42 UTC, martin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description martin 2015-01-12 20:42:44 UTC
Created attachment 151483 [details]
port directory contents: security/hs-pam

Hi,

I've made a new port: security/hs-pam. The software makes PAM bindings available for Haskell.

It is not documented very well, but from the source and from the types, I could make a small test program that checked its functionality. It worked for the purpose of authentication.
Comment 1 Gabor Pali freebsd_committer freebsd_triage 2015-01-18 12:03:47 UTC
Have you been using this port or are you planning to use this in the near future?  I think I have already met this hackage before, but things like the definition of the `checkAccount` function [1] scared me.  It looks also old and unmaintained.

[1] http://hackage.haskell.org/package/pam-0.1/docs/src/System-Posix-PAM.html#checkAccount
Comment 2 martin 2015-01-18 12:48:24 UTC
I am thinking about writing a display manager in Haskell and collecting stuff to make it possible. I will certainly need PAM bindings at some places, at least the authentication function. I verified that it works (positive and negative test).

Yes, this checkAccount function is certainly crap, but it does not look like it's used somewhere and I see that it's useless.

Do you have any alternative to do system authentication on FreeBSD from Haskell code? This is the only library I have found so far.
Comment 3 Gabor Pali freebsd_committer freebsd_triage 2015-01-18 13:12:52 UTC
Right off the top of my head, I cannot tell you any better alternatives either unfortunately.  I was just curious if you are fully aware of its state and you have any specific reason to include this in the Ports Collection.  But I do not have any objections in general.
Comment 4 martin 2015-01-19 07:12:18 UTC
I cannot decide now, after you pointed out the problem.

Since the module has got a permissive license (BSD 3-clause), I could integrate it directly into my project (and eventually fix it) without having a dependency on it. It's also acceptable, I think. I also just need the one authentication function that works.

You can close my request without adding hs-pam, if you want. It is not urgent/necessary to have it in the ports tree.
Comment 5 Gabor Pali freebsd_committer freebsd_triage 2015-01-19 18:46:18 UTC
Okay, let us not include this port for now.