| 1 |
On Wednesday 06 April 2005 23:38, Martin Schlemmer wrote: |
| 2 |
> > - we need an ebuild for openpam (i've wrote one, but still misses a few |
| 3 |
> > points, mainly for the missing thigns here stated) |
| 4 |
> And you/bsd_peeps will obviously maintain it. |
| 5 |
Sure, as I said I'm taking care of it and I'll do for all the time I can. |
| 6 |
|
| 7 |
> > openpam will pdepend on |
| 8 |
> > freebsd-pam-modules to provide both in a simple way. |
| 9 |
> Why? What good will they do on linux? Just stick them in bsd profile. |
| 10 |
Mainly, openpam is shipped without any kind of module. If someone would like |
| 11 |
to replace Linux-PAM with openpam on a Linux system (it's possible), I'd much |
| 12 |
prefer to provide it with everything he needs. Linux-PAM builds its own |
| 13 |
modules, openpam just provide pam implementation and needs other packages to |
| 14 |
provide the basic modules. FreeBSD's modules should work on Linux and this |
| 15 |
would make possible the switch between Linux-PAM and openpam. |
| 16 |
|
| 17 |
> Like I said before, only real reason why I will biatch about this one, |
| 18 |
> is its called 'pam' on all linux distro's, and it will be another lost |
| 19 |
> history (ok, so the workaround is a schlepp) case without real cause. |
| 20 |
Actually it's called libpam usually :) |
| 21 |
Mainly, calling it pam is usual on linux-centric systems, but as Gentoo is not |
| 22 |
only Linux, and "it's all about choice", having it called as it's named, |
| 23 |
IMHO, is a way to state clearly what it is. |
| 24 |
Just take a look to telnet-bsd and netkit-telnetd. On Debian there's |
| 25 |
netkit-telnet which is called just telnet. |
| 26 |
Anyway this is only "cosmetic" and for what I "need" or better I feel is |
| 27 |
needed, this is something which can be omissed. |
| 28 |
|
| 29 |
> Ugh, no - just more crud that somebody will have to clean out later. |
| 30 |
> Like I said, get pam-0.78 and issues fixed, bumped to stable on all |
| 31 |
> linux archs, and we can scourge the tree. |
| 32 |
That's a decision up to you as pam mantainers :) |
| 33 |
Anyway I'm available to add the temporary fixes, trace them, and remove them |
| 34 |
when all is done, if needed. |
| 35 |
|
| 36 |
> > I'll work anyway on a pam_stack hack for openpam, also if I'm not sure |
| 37 |
> > if, when and how I'll be able to make it work... also I don't like too |
| 38 |
> > much messing with security stuff :/ |
| 39 |
> Sorry, you are on your own here. |
| 40 |
I know and I'll try to do everything I can, but if in the mean time it could |
| 41 |
be used the other method should be enough until there's a way to "support" |
| 42 |
pam_stack on openpam. |
| 43 |
|
| 44 |
-- |
| 45 |
Diego "Flameeyes" Pettenò |
| 46 |
http://wwwstud.dsi.unive.it/~dpetteno/ |
Archives