On Thursday, May 2, 2002, at 12:56 , Mark Murray wrote:
For me, nowadays 45MB is nothing compared to medium HDD capacity, and
even
my POCKET PC will easily accomodate it...
45 MB is fine as a port - we have ports that are way bigger than that.
And we even have bigger ports
name, like:
smallperl
modestperl
tightperl
midgetperl
petiteperl
Sure, whatever. Smallperl it is. :-)
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
#text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc
#application/octet-stream
.
There is merit to this point - make Perl5 a super-port (or
something), that is closer to the OS than a usual port but not part
of the base OS. I have no objection to this.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
#text/plain; name=cv.doc [Mark Murray CV Plain Text
-freebsd
... etc. I could do this.
Secondly, as the above message indicates, there should be a full Perl
installation available, using whatever packaging method is used by the
OS distribution.
FreeBSD has the ports collection that has a full install of Perl 5.6.1.
M
--
o Mark Murray
\_
O
:-)
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
#text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc
#application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
fully recognise as a programmer that this is not trivial work :-).
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
for this opportunity to discuss this
thorny issue with you!
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
How can I find out which binaries have changed?
they are all different according to cksum so I assume
that there is a timestamp or something in them.
Is there a way to compare only the text segments?
You can do wonders with objdump(1) and diff.
and ident(1).
M
--
o Mark Murray
gcc31 for testing).
Gotcha.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Is there an #include sys/types.h missing in pam_opieaccess.c?
Yes. Added now.
Thanks!
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I have fixed this and these by making lint(1) a cross-tool.
Excellent!
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, which works, to see if I can't fix
undump.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
the reason for the program to segfault, I
even opened a PR on that. The program seems to work on NetBSD btw.=20
PR ports/34661 :-)
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
The recent changes to ipfilter break world. Can
someone back out the changes?
Better; please post the errors that you are seeing so that this can
be fixed.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
.
Post the _errors_. :-)
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
://www.oracle.com Enabling The Information Age
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The perl upgrade seems to be having problems. I got this twice
towday making buildworld from 4.5:
Please test the enclosed patch.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
Index: config.SH-elf.alpha
cc1: warnings being treated as errors
# make NO_WERROR=yes ...
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hello all
The system perl has been upgraded to Perl 5.6.1. This means that
it is a _very_ good idea to rebuild all your p5-* ports. As usual,
if there are any problems, I want to know about them.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
#application/octet-stream
terminated with signal 11, Segmentation fault.
#0 0x0 in ?? ()
(gdb) where
#0 0x0 in ?? ()
#1 0x8181578 in __do_global_ctors_aux ()
#2 0x80480b6 in _init ()
(gdb)
Any ideas?
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
/libexec/rtld-elf/rtld.c:380
Other ports (like QT2) are also doing this.
Any ideas?
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
#application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf
#text/plain; name=cv.txt [Mark Murray CV Plain Text] cv.txt
To Unsubscribe
, there are some other makefiles and mtree things that
need to be done. Also the ports will be affected (not by very much).
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
This comment is false. On my -CURRENT system with
this commit in place 'passwd' and 'login'/'su' commands
loops forever computing MD5 password.
After reverting crypt-md5.c to rev. 1.8 all thouse
commands work as always.
It was a signed/unsiged issue. Fixed!
M
--
o Mark
due to it and this just isn't acceptable even for
-current.
That is _my_ fault, not DES'. It was a crypt() problem which I have fixed.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
it if you have the bad version of crypt-md5.c(1.9)
and you actually use md5 passwords (the salt begins with $1$ when
you look in /etc/master.passwd). The breakage time was less than
24 hours.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
a hour that I spent debugging what's going wrong.
My apologies. I should have thought to do that.
I'll remember if there is a next time ;-)
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
#include pam_mod_misc.h
to #include secure/pam_mod_misc.h without ensuring that a (correct)
pam_mod_misc.h was in an appropriate secure/ dir.
I've just finished fixing this (includes a repo-copy) and it will go
in shortly.
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
Mark Murray [EMAIL PROTECTED] writes:
The problem is in the headers; you changed #include pam_mod_misc.h
to #include secure/pam_mod_misc.h without ensuring that a (correct)
pam_mod_misc.h was in an appropriate secure/ dir.
Umm, IIRC 'make world' starts by doing a 'make includes
Mark Murray [EMAIL PROTECTED] writes:
Umm, IIRC 'make world' starts by doing a 'make includes' into
/usr/obj, which should take care of this.
That is 'make world'. It was broken for make obj make depend make,
[...]
IMO, the repo-copy is the cleanest, because it solves te above
It would be nice to see this version of perl in -CURRENT. It would help
ease the development of mod_perl-2.0 by not having to install the port
and it just makes sense considering the bleeding-edge of the rest of the
system.
Coming RSN. Maybe this weekend.
M
--
o Mark Murray
hang out, and in an ideal world I see an need
for (new) warnings to break things. I see no need for warnings to
hold back a project as important as GCC3, and NO_WERROR is the
cleanest solution.
I do not expect others to agree with (or like) this.
M
--
o Mark Murray
\_ FreeBSD Services
On Wed, Feb 06, 2002 at 11:12:38AM +, Mark Murray wrote:
IMO, this is a good reason to not have WARNS contain -Werror at this
time. NO_WERROR is a good way to fix this (again IMO). I see a great
need to let warnings hang out, and in an ideal world I see an need
for (new) warnings
hang out, and in an ideal world I see an need
for (new) warnings to break things. I see no need for warnings to
hold back a project as important as GCC3, and NO_WERROR is the
cleanest solution.
I do not expect others to agree with (or like) this.
M
--
o Mark Murray
\_ FreeBSD Services
On Wed, Feb 06, 2002 at 11:12:38AM +, Mark Murray wrote:
IMO, this is a good reason to not have WARNS contain -Werror at this
time. NO_WERROR is a good way to fix this (again IMO). I see a great
need to let warnings hang out, and in an ideal world I see an need
for (new) warnings
+172,5 @@
#ifndef _POSIX_SOURCE
-#define NBBY8U /* number of bits in a byte */
+#define NBBY8 /* number of bits in a byte */
/*
%%%
Bruce
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I'm experiencing the following error while bulding world:
Fix committed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The patch is attached.
Thanks! Committed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Now that current on Alpha builds a lot better than a
few days back it fails in:
cc -nostdinc -O -pipe -mcpu=ev4 -mcpu=ev4
-I/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/include
Already fixed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning
in your mailer.
Todays error:
=== libpam/modules/pam_ssh
Already fixed. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
in -CURRENT?
I didn't think that we did.
No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked
against Heimdal.
I'm testing the fix, and will commit in a day or two.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
On Wed, Jan 30, 2002 at 01:47:24PM +, Mark Murray wrote:
No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked
against Heimdal.
I'm testing the fix, and will commit in a day or two.
OK, great. I assume you'll import it on the vendor branch?
Yup!
M
--
o
*pamh, int flags, int argc, const char **argv)
+{
+ struct options options;
+
+ pam_std_option(options, NULL, argc, argv);
+
+ PAM_LOG(Options processed);
+
+ PAM_RETURN(PAM_IGNORE);
+}
+
+PAM_MODULE_ENTRY(pam_opieaccess);
--=-=-=--
--
o Mark Murray
and not in contrib/opie. If you care about
machine independance, better use opielookup() directly.
No, that is OK. :-)
The FreeBSD PAM modules are all written from scratch as BSD PAM modules.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
automated scripts processing.
I have idea to solve it adding no_fake_prompts option to pam_opie to
control that per admin choice.
Yes. That would be a good move. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail
.
I believe pam_get_pass() should set PAM_AUTHTOK. Any objections?
Not from me :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Here are the (hopefully) final patches. Any final objections before I
commit the lot?
According to EyeBall Mk1, this is fine! :-)
I haven't extensively tested the code, but the methods used and the
design are very sound, I believe.
M
--
o Mark Murray
\_ FreeBSD Services Limited
) = pwd-pw_expire)
+ retval = PAM_AUTH_ERR;
}
else {
--
Andrey A. Chernov
http://ache.pp.ru/
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
';
if (suser_override)
--
Andrey A. Chernov
http://ache.pp.ru/
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, response, sizeof resp);
/*
* Opieverify is supposed to return -1 only if an error occurs.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD
On Sun, Jan 20, 2002 at 19:47:55 +, Mark Murray wrote:
Do you mean that at at the very edge of password expiry, the user may
still be able log in (maybe some seconds later)? If so this is not a
credible threat.
Yes. Few seconds can be few hours or more in case network is down
On Sun, Jan 20, 2002 at 19:55:31 +, Mark Murray wrote:
This works, but strikes me as overkill. This is salt, not cryptographic
randomness, so 'srandom(junk)' is most likely better as a replacement
for srandomdev() (where 'junk' can be time(), pid or anything similar).
You can't
code that cares about the state should do the same.
True but not trivial. I'd be happy to commit working patches :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
On Sun, Jan 20, 2002 at 23:14:13 +, Mark Murray wrote:
The PAM OPIE may only do OPIE authentication. It is entirely up to the
PAM stack to decide what the login policy is.
(Well, the PAM stack as specified by the pam configs in /etc/pam*)
Yes. And to allow PAM stack to make
On Sun, Jan 20, 2002 at 23:44:44 +, Mark Murray wrote:
Yes. And to allow PAM stack to make right decision, pam_opie pass special
information to PAM stack. Look at the patch, pam_opie not breaks from the
stack by yourself, it is /etc/pam* do that using information from
pam_opie
for modules which
have no authentication (like say, pam_motd, which prints /etc/motd
during the pam_session_open() phase). IGNORE may have other uses,
but I can't remember them offhand.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
will not change
_at_all_.
There will be no SRA unless you install secure/ telnet.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
! This will make src/crypto mandatory
if you want telnet(d). This will _not_ make crypto _use_ mandatory.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Well, it would seem that the cu upgrade has totally hosed cu now:
# cu -l /dev/cuaa1 -s 9600
usage: tip [-v] [-speed] [system-name]
Can we get this fixed please?
Yes.
Import coming.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
There is already a patch in PR ports/30899. It is OK to commit it
IF you can test it first on a FreeBSD 4.x system (any architecture)
and also a -current Alpha system.
Cool! Thank you!
M
John
Mark Murray wrote:
John
I have a patch (courtesy of Brian Somers) that fixes M3. I
Erm, it _is_ fixed in the makefile. If you have a better method, lets hear
it. :-)
Back out the entire tip commit? This would also restore all the FreeBSD
changes clobbered by it. It doesn't even compile cleanly:
Entirely different problem.
M
--
o Mark Murray
\_ FreeBSD
] Sunbay Software AG,
[EMAIL PROTECTED]FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.orgThe Power To Serve
http://www.oracle.com Enabling The Information Age
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
I have installed application software from port collection . How do I
make un-install ? If I want to upgrade the existing application , how do I
upgrade them ? Please advise
Please ask this question on [EMAIL PROTECTED]
M
--
o Mark Murray
\_ FreeBSD Services Limited
O
cp='cp -i'
alias mv='mv -i'
alias rm='rm -i
Another question , what is the function of PS2 and when to use it ? Please
advise
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD
Mark, please back your 1.32 revision from share/examples/Makefile out,
Done.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
:-).
Actually, it is possible for there to be no copies: target in
src/share/examples/something. The copies: (actually copies::)
target is built up in a .for loop that may be empty.
The fix is a dummy copies:: target.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig
Forgot to mention, I had to make kcheckpass setuid root to make kcheckpass
itself work (just verified this on -stable).
Yes - this is documented. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
in /usr/src/kerberos5/libexec.
*** Error code 1
Stop in /usr/src/kerberos5.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Should I file a PR?
No. I have this :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems that we dont have a /usr/lib/pam_rhosts_auth.so.
Yes - I need to write one.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-v_interlock);
I get exactly the same thing.
Manual bactrace is:
panic
witness_unlock
_mtx_unlock_flags
vop_nolock
vop_defaultop
vn_lock
ffs_mountfs
ffs_mount
vfs_mountroot_try
vfs_mountroot
mi_startup
begin
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap
if opiechallenge() is
failed.
I don't know how it should work with OPIE. Could you please fixing
this, Mark?
Sure! I've never used rexecd, su could you please suggest a minimalist
test/command that I could use, and I'll get right to it. :-)
M
--
o Mark Murray
\_ FreeBSD Services
: card inserted, slot 0
reset 1
int is 0 stat is ff
pccard: card inserted, slot 1
reset 1
int is 0 stat is ff
reset 2
int is 60 stat is ef
reset 2
int is 60 stat is cf
reset 3
int is 60 stat is ef
reset 3
int is 60 stat is ef
sio1 at port 0x2f8-0x2ff irq 3 slot 0 on pccard0
sio1: type 16550A
M
--
Mark
the correct root FS))
If I undef acpi_load at boot, the system boots fine.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
As far as I can tell, there's nothing in the tree which uses libss any
longer, and hasnt been for quite some time. Is there any reason to
keep it?
Nope.
Right. Kill it.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
at
a later stage.
I have already asked for reviews on -audit. Those who are looking at my
patches should download again, because I have done some further fixes
and improvements.
I'll commit in three days from the date of this email if nothing comes
up.
M
--
Mark Murray
Warning: this .sig is umop ap
Does anyone know what changed?
(someone has suggested the change came about when PAM's session model was
changed)
Following up on my previous message; I've asked re@ for permission
to MFC the fix.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
I need to MFC login(1) some more. Please try that, and if it
works, lets get it committed.
STABLE's PAM modules and support are quite a bit behind CURRENT's.
What are your /etc/pam.conf entries for login? See if borrowing
any CURRENT entries helps you.
M
--
Mark Murray
Warning: this .sig
According to Mark Murray:
Can you make it so that if NO_OPENSSL is not defined, then openssl is used?
I could of course but I don't think that having PUBKEYS by defaults (X.509
based, not the PGP ones) is probably not very useful yet as it is a fairly
recent option.
AUTOKEY should
an optional component.
I'm a bit reluctant to force openssl for just ntpd.
Can you make it so that if NO_OPENSSL is not defined, then openssl is used?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
hope, before PAM use in su
is MFC'd.
I have just entered a PR on this.
cc'd to: markm
Joshua
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
Xwrapper
I'm not sure I follow you here...
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Why? Better way will be rewritting ports to use good-new OPIE.
wi-ftpd already have OPIE hooks, but I not sure they works. Popper needs
modifications. Doesn't know, if other ports using Skey exists.
I can do base software, but I haven't time to fill all ports.
M
--
Mark Murray
Warning
no water - the BSD books that I have point to MH and
Emacs in the same way.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I've noticed that new PAM segfaults when I'm typing non-existing login
at console login prompt. Please fix.
This current, right? I'll sort it out. Thanks for the debug-sleuthing!
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
: 7bit
Content-Disposition: inline;
filename=misc_conv.c.diff
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Is there any plan to port pam_ldap ( and nss_ldap )
to FreeBSD-CURRENT ?
No plans, but if you submit something, I would be interested.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Hi
Those who made a buildworld without NO_PERL=true with sources
newer than Tue, 1 May 2001 02:25:25 -0700 (PDT), but older than
2001/05/02 14:18:33 PDT, must apply the following patch as root in
/usr/libdata/perl/BSDPAN directory.
(If you are tracking CURRENT, then CVSup and/or cvs update
was one).
Those patches of yours look reasonable.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
. For one, KERBEROS is no
longer needed. (fixed locally). WHEELSU needs to be properly documented.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I update 4.3 RC to 5.0-CURRENT and have some troubles.
Why make buildworld build system without RSA support ?
And how i can correct this problem ?
System cvsuped today.
Go to /dev and remake all your devices.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail
stuff was disabled?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
201 - 300 of 686 matches
Mail list logo
