New port: net/zerotier

[Corey Smith]

Please commit:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203161

-Corey Smith
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Apache 2.2 + mod_auth_pam + PAM

[Corey Smith]

On 5/3/07, Jonathan Weiss <[EMAIL PROTECTED]> wrote:


I'm struggeling with setting up Apache 2.2 and mod_auth_pam to
authenticate an BasicAuth directory against my local unix users.




I'm using pam authentication with apache 2.2.  We mostly use radius for
authentication but here is my config:

$ cat /etc/pam.d/httpd
#
# PAM configuration for the "httpd" service
#

# auth
authrequiredpam_nologin.so  no_warn
authsufficient  pam_radius.so   no_warn
try_first_pass
authrequiredpam_unix.so no_warn
try_first_pass

# account
account requiredpam_login_access.so
account requiredpam_unix.so

# session
session requiredpam_permit.so

# password
passwordrequiredpam_unix.so no_warn
try_first_pass

# relevant httpd.conf:

LoadModule auth_pam_modulelibexec/apache2/mod_auth_pam.so
LoadModule auth_sys_group_module libexec/apache2/mod_auth_sys_group.so

Alias /wordpress "/usr/local/www/data/wordpress"

  AuthType Basic
  AuthName "Secure Area"
  AuthGroupFile /usr/local/etc/apache2/groups
  Require group group1

  DirectoryIndex index.php


$ cat /usr/local/etc/apache2/groups
group1: corsmith

BTW: I don't believe you need to mess around with changing permissions on
any of the password files:

$ ls -l /etc/passwd /etc/master.passwd /etc/spwd.db
-rw---  1 root  wheel   1248 Apr 1 11:35 /etc/master.passwd
-rw-r--r--  1 root  wheel   1022 Apr 1 11:35 /etc/passwd
-rw---  1 root  wheel  20960 Apr 1 11:35 /etc/spwd.db

-Corey Smith
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: A review of different port management tools : analysis for Google SoC project

[Corey Smith]

Ramblings of a long time FreeBSD user:

* Use the pkg_* tools to manage the system binaries too:

Imagine if installing the man pages would be as easy as:

pkg_add -r freebsd-6.1-man

or upgrading from 6.1-RELEASE to 6.2-RELEASE:

portupgrade -o system/freebsd-6.1 freebsd-6.2

even better (use packages):

portupgrade -PP -o system/freebsd-6.1 freebsd-6.2

See if anybody modified any system files:

pkg_info -x ^freebsd6 -g

* Make a cvs / portsnap tag that allows you to follow the tag of the
last successful binary builds

This way your ports collection and the binary packages available at
$PACKAGEROOT are in sync.  portupgrade -PP will have more success and
it will make things like a gettext shlib bump easier to deal with.

-Corey Smith
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"