Bug 204596 - [NEW PORT] security/pam_pkcs11: PAM module with PKCS#11 token support
Summary: [NEW PORT] security/pam_pkcs11: PAM module with PKCS#11 token support
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Martin Wilke
URL:
Keywords: feature, needs-qa, patch
Depends on:
Blocks:
 
Reported: 2015-11-16 13:35 UTC by Steve Vickruck
Modified: 2017-05-07 11:18 UTC (History)
1 user (show)

See Also:


Attachments
pam_pkcs11 (46.29 KB, text/plain)
2015-11-16 13:35 UTC, Steve Vickruck
no flags Details
pam_pkcs11 shar archive (46.30 KB, text/plain)
2015-11-16 14:06 UTC, Steve Vickruck
no flags Details
poudriere testport log for pam_pkcs11-0.6.8 (102.23 KB, text/plain)
2015-11-16 14:07 UTC, Steve Vickruck
no flags Details
Code changed upstream (16.62 KB, patch)
2015-11-18 10:12 UTC, Steve Vickruck
no flags Details | Diff
pam_pkcs11 shar archive (30.97 KB, text/plain)
2016-01-11 14:41 UTC, Steve Vickruck
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Vickruck 2015-11-16 13:35:38 UTC
Created attachment 163191 [details]
pam_pkcs11

New port: security/pam_pkcs11
Comment 1 Steve Vickruck 2015-11-16 14:06:13 UTC
Created attachment 163194 [details]
pam_pkcs11 shar archive
Comment 2 Steve Vickruck 2015-11-16 14:07:32 UTC
Created attachment 163195 [details]
poudriere testport log for pam_pkcs11-0.6.8
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-16 16:50:49 UTC
Thanks Steve!
Comment 4 Steve Vickruck 2015-11-18 10:12:36 UTC
Created attachment 163286 [details]
Code changed upstream

Previous distfile broken due to upstream code changes

Modified:
  Makefile: changed GH_TAGNAME to 8bdd819; bumped PORTREVISION to 1
  distinfo
Deleted:
  files/patch-src_pam__pkcs11_Makefile.am (fixed upstream)
  files/patch-src_pam__pkcs11_pam__pkcs11.c (fixed upstream)
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-11-18 10:16:16 UTC
@Steve, can you obsolete the attachment you no longer want to be referenced please. You can do so by clicking Attachment "Details -> "Edit Details" -> [X] Obsolete
Comment 6 Martin Wilke freebsd_committer freebsd_triage 2016-01-10 13:37:43 UTC
Close; Feedback timeout 3 months+
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2016-01-10 13:41:48 UTC
Feedback was received, re-open.
Comment 8 Kubilay Kocak freebsd_committer freebsd_triage 2016-01-10 13:53:28 UTC
@Steve, I apologise for missing it before, but since the port does not exist in the tree, we need a complete shell archive (man shar) to create the port. At the moment attachment 163286 [details] is a diff of the original shar, which we obsoleted.

Can you please attach a full shar of the port again, that includes the second version changes.

Thanks!
Comment 9 Steve Vickruck 2016-01-11 14:41:37 UTC
Created attachment 165395 [details]
pam_pkcs11 shar archive
Comment 10 Steve Vickruck 2016-01-11 14:42:18 UTC
(In reply to Kubilay Kocak from comment #8)

No worries; I've attached an updated shar archive.
Comment 11 Martin Wilke freebsd_committer freebsd_triage 2017-05-06 09:53:12 UTC
Hi,

Would u mind to update the port to the current ports standard?