On Sun, 30 Jul 2000, Chris Costello wrote:
> On Sunday, July 30, 2000, Leif Neland wrote:
> > Freshly cvsupped current.
> >
> > Sendmail 8.11.0
> >
> > When invoking sendmail or newaliases I get this message:
> > /etc/pwd.db: Invalid argument
> >
> > Sendmail can't read /etc/pwd.db, and ther
> Mark already stated that in *practicality*, Yarrow-BF-cbc-256 1.0
> (I guess that's the proper name for this :-) is complex enough and
> generates good enough ouput. If you /really/ want to make the attack
> on it much harder, how about this: if you're going to read 1024 bits
> of entropy from
> Content-Disposition: attachment; filename="yarrow_blocking.patch"
Brian:
I want to take a different approach to this one.
Do not commit anything to the /dev/random device, please, without running
it by me.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: s
I am really uncertain where to set the reply-to to.
I don't read ports though.
Anyways.
I have been using snes9x 1.26 some time ago on my CURRENT box and
everything worked ok.
Today, after I updated my CURRENT this weeks from a month old to
something more recent, I figured I should install snes
On Sun, 30 Jul 2000, Mark Murray wrote:
> > Content-Disposition: attachment; filename="yarrow_blocking.patch"
>
> Brian:
>
> I want to take a different approach to this one.
>
> Do not commit anything to the /dev/random device, please, without running
> it by me.
I was not planning on it. Yo
Hi,
pam_ssh isn't able to start ssh-agent if you use
---snip---
xdm session sufficient pam_ssh.so
---snip---
in /etc/pam.conf. With "malloc.conf -> aj" it seems to work.
grep pam /var/log/messages:
---snip---
Jul 30 00:54:04 Magelan -:0: unable to resolve symbol: pam_sm_chauthtok
Jul 30 00:54:05
On Sun, 30 Jul 2000, Jeroen Ruigrok/Asmodai wrote:
> I am really uncertain where to set the reply-to to.
> I don't read ports though.
>
> Anyways.
>
> I have been using snes9x 1.26 some time ago on my CURRENT box and
> everything worked ok.
>
> Today, after I updated my CURRENT this weeks from
On Sun, 30 Jul 2000, Mark Murray wrote:
> This is a reversion to the count-entropy-and-block model which I have
> been fiercely resisting (and which argument I thought I had sucessfully
> defended).
>
> My solution is to get the entropy gathering at a high enough rate that
> this is not necessar
> > Do not commit anything to the /dev/random device, please, without running
> > it by me.
>
> I was not planning on it. You really should take a look at the bugfixes,
> though; reading buffer sizes of >8 bytes but not-8-byte-multiple should
> do it. There's also the ioctl handler which you ne
> How does entropy gathering at a high enough rate solve this
> particularly?
EG, by having it such that Yarrow state perturbations happen often
enough that each read is "guaranteed" to be associated with at least
one and preferably more.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.
On Sun, 30 Jul 2000, Mark Murray wrote:
> > How does entropy gathering at a high enough rate solve this
> > particularly?
>
> EG, by having it such that Yarrow state perturbations happen often
> enough that each read is "guaranteed" to be associated with at least
> one and preferably more.
Can
> > EG, by having it such that Yarrow state perturbations happen often
> > enough that each read is "guaranteed" to be associated with at least
> > one and preferably more.
>
> Can you give me an idea how this would work, at least with e.g.
> pseudocode annotation of the current code? I'm curiou
weird, works fine for me here
-trish
__
Trish Lynch
FreeBSD - The Power to Serve[EMAIL PROTECTED]
Rush Networking [EMAIL PROTECTED]
On Sun, 30 Jul 2000, Leif Neland wrote:
>
>
> On Sun, 30 Jul 2000, Chris Costello wrote:
>
> > On Sunday, July 30, 200
-On [2730 19:47], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote:
>On Sun, 30 Jul 2000, Jeroen Ruigrok/Asmodai wrote:
>
>> I cannot remember exactly when I last used snes9x, but my
>> .snes96_snapshots/ directory shows february as the last savedates.
>
>Defini
Hello,
On Sun, Jul 30, 2000 at 02:24:38AM +0200, Benedikt Schmidt wrote:
> On Wed, Jul 26, 2000 at 11:12:34PM -0400, Alexander N. Kabaev wrote:
>
> The patch solves the problem here too. Perhaps it could be added to the other
> FreeBSD patches in the XFree86-4 port.
I have sent it already to the
< said:
>> On Sunday, July 30, 2000, Leif Neland wrote:
>> > Sendmail 8.11.0
>> >
>> > When invoking sendmail or newaliases I get this message:
>> > /etc/pwd.db: Invalid argument
>> >
>> > Sendmail can't read /etc/pwd.db, and therefore cannot deliver any local
>> > mail.
>> >
>> > Howtofixitp
-On [2730 19:47], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote:
>What color depth are you running at? I wouldn't expect that anything
>16-bit or higher wouldn't work well, at least. -CURRENT usually works
>great for gaming for me; I'm going through, e.g., C
On Sun, 30 Jul 2000, Mark Murray wrote:
> This is a reversion to the count-entropy-and-block model which I have
> been fiercely resisting (and which argument I thought I had sucessfully
> defended).
Actually, I was waiting for your reply to Jeroen's question about changing
the semantics of the r
Hi,
I updated my source tree yesterday (and kernel) and am having some problems
with my keyboard under X. Has anyone else noticed anything
strange.
steve
--
Steve Heistand
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
I have, like when I'm running tail on something, and then I try to ctrl-c
out of it, the whole console locks solid, and I have to reboot. (although
if I was connected to an ethernet, I think I could probably ssh in and
reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the
lockmg
The problem I am seeing is that the keyboard isnt even seen.
Its useable up until about midway through the boot process,
then it goes dead/locks up. The boot continues fine and the machine
is up. The mouse is usable in X but not the keyboard. Cant even switch
virtual consoles.
steve
> I have
Hrmm, that's even worse than my problem.
=
| Kenneth Culver | FreeBSD: The best NT upgrade|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: muythaibxr
My last grip about this didn't draw any response except for "Yeah, I
have that problem to". Is there a better place to discuss problems
with the Perl integration with FreeBSD? send-pr doesn't have a "perl"
category, or I'd try that.
Basically, the problem is that ports that install Perl modules i
Alexander Leidinger wrote:
>
> Hi,
>
> pam_ssh isn't able to start ssh-agent if you use
> ---snip---
> xdm session sufficient pam_ssh.so
> ---snip---
> in /etc/pam.conf. With "malloc.conf -> aj" it seems to work.
>
> grep pam /var/log/messages:
> ---snip---
> Jul 30 00:54:04 Magelan -:0: unable
On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:
> The problem I am seeing is that the keyboard isnt even seen.
> Its useable up until about midway through the boot process,
> then it goes dead/locks up. The boot continues fine and the machine
> is up. The mouse is usable in X but not the keyboard.
(Originally didnt response back to mailing list...)
The keyboard works fine when I dont start X, single user mode
or just at the console. I can crash the machine whenever I switch
virtual consoles which is most not fun. Not sure if its
strictly an X problem on not.
My previous -current was bef
My problems are with a previous build of late last week. And my problem
isn't with X. My problem only happens when you start "tail" on some file,
then try to exit. It locks the console solid... neither the mouse nor the
keyboard work.
=
To resolve the problem with tail, rebuild your kernel with revision 1.11 of
sys/kern/kern_event.c. 1.12 which was designed to make the kevent system
restartable seems to keep the process from ever receiving the interrupt. I
don't have a solution which solves both problems yet.
Jim Bloom
[EMAIL
On Sun, 30 Jul 2000, Alexander Leidinger wrote:
> Hi,
>
> pam_ssh isn't able to start ssh-agent if you use
> ---snip---
> xdm session sufficient pam_ssh.so
> ---snip---
> in /etc/pam.conf. With "malloc.conf -> aj" it seems to work.
I've seen problems like this (try using Konqueror with malloc.c
I didn't have much time for testing, but backing out this change fixes the
problem tail. For some reason, the signal never gets delivered to the process.
The manual page states that the kevent processing is lower priority than signal
handling and that the signal will get processed as normal befor
I did a little more testing of this problem just now. A SIGKILL does not kill
the process but will lock up the machine. Truss reports the SIGKILL being
continuously sent to the process. If I break into DDB, and then panic, I get a
panic "lockmgr: pid XXX, not exclusive lock holder 0 unlocking".
On Sun, 30 Jul 2000, Kenneth Wayne Culver wrote:
> My problems are with a previous build of late last week. And my problem
> isn't with X. My problem only happens when you start "tail" on some file,
> then try to exit. It locks the console solid... neither the mouse nor the
> keyboard work.
Sorr
> On Sun, 30 Jul 2000, Mark Murray wrote:
>
> > This is a reversion to the count-entropy-and-block model which I have
> > been fiercely resisting (and which argument I thought I had sucessfully
> > defended).
>
> Actually, I was waiting for your reply to Jeroen's question about changing
> the se
33 matches
Mail list logo
