On Thu, 9 Jul 2020, Theo de Raadt wrote:
static const struct urng_type urng_devs[] = {
{ { USB_VENDOR_OPENMOKO2, USB_PRODUCT_OPENMOKO2_CHAOSKEY },
{64, 5, 0, 100, 5000} },
Interesting. That's what became of OpenMoko... a pool of DevIDs
for small device builders?
m
Daniel Jakots wrote:
> On Thu, 09 Jul 2020 16:35:13 -0600, "Theo de Raadt"
> wrote:
>
> > > PS I think the USB devices are probably a pretty good source of
> > > true entropy.
> >
> > Why do I bother explaining? I'm the maintainer of the openbsd
> > kernel's randomness code. I say I
--- Theo de Raadt wrote:
> And I went out of my way to politely explain it to you
I would like a more detailed explanation, because I don't yet understand.
That's why I asked for literature I could read.
Thanks,
Ken
CONFIDENTIALITY NOTICE: This email and any attachments are for the sole
Hello everybody,
introducing this little ansible role to configure hostname.if(5) files.
comments are welcome
https://github.com/gred7/ansible-openbsd-interfaces-role.git
--- Theo de Raadt wrote:
> And I don't give a rats ass about a cheap-ass garbage usb device
> that can't even afford to allocate a proper usb device ID.
> I don't care.
I get that you think I'm wrong (and maybe I am!)
but I don't yet understand why.
Can you point me to some literature on the
I wrote:
>> How do I use a hardware random number generator to
>> continuously seed /dev/random with new truly random numbers?
--- Theo de Raadt wrote:
> We consider these devices boring, because the kernel does a good enough job
> creating random.
> randomness only has a bootstrap problem. And
I have a few TrueRNG hardware random number generators.
They are USB devices, and generally appear as modems.
How do I use them to continuously seed /dev/random with new truly random
numbers?
It's got to be something very simple like
tail -f /dev/TrueRNG > /dev/random
or something like that.
I appreciate your help!
Either you solved the previous problem telling me to put $ORIGIN in my BIND
zone files,
or I had made a mistake with the 'set port=number' command in nslookup.
In either case NSD is now working properly in both directions.
But Unbound is only working correctly in the
On Thu, 09 Jul 2020 16:35:13 -0600, "Theo de Raadt"
wrote:
> > PS I think the USB devices are probably a pretty good source of
> > true entropy.
>
> Why do I bother explaining? I'm the maintainer of the openbsd
> kernel's randomness code. I say I don't see the point in 1 line of
> code to
wrote:
> --- Theo de Raadt wrote:
> > And I went out of my way to politely explain it to you
>
> I would like a more detailed explanation, because I don't yet understand.
>
> That's why I asked for literature I could read.
We publish our source tree, which contains the complete random
number
wrote:
> --- Theo de Raadt wrote:
> > And I don't give a rats ass about a cheap-ass garbage usb device
> > that can't even afford to allocate a proper usb device ID.
> > I don't care.
>
> I get that you think I'm wrong (and maybe I am!)
> but I don't yet understand why.
We are not going to
wrote:
> I wrote:
> >> How do I use a hardware random number generator to
> >> continuously seed /dev/random with new truly random numbers?
>
> --- Theo de Raadt wrote:
> > We consider these devices boring, because the kernel does a good enough job
> > creating random.
> > randomness only has
We consider these devices boring, because the kernel does a good enough
job creating random.
randomness only has a bootstrap problem. And these devices don't solve
the bootstrap problem.
wrote:
> I have a few TrueRNG hardware random number generators.
> They are USB devices, and generally
Nope. I still don't have it working.
NSD is working in both directions.
Unbound is only working in the forward direction.
Here is proof that both Unbound and NSD are working in the forward direction:
7 Soekris2#
please disregard this. as expected, if one mentions 'typo' it is
inevitable that one will embarrass themselves profoundly. as it happens
i read the config too quickly and entirely wrongly.
On Thu, 9 Jul 2020 15:21:27 -0400, Amelia A Lewis wrote:
> On Thu, 9 Jul 2020 17:44:48 +,
On Thu, 9 Jul 2020 17:44:48 +, ken.hendrick...@l3harris.com wrote:
> name: 2.168.192.in-arpa.arpa.
^
It's a mystery, as well, why you would set up nsd (an authoritative
sever) if you're not delegating to it in the recursive/caching server.
But if
I asked:
>> nsd works only in the forward direction: from a name to an IP address.
>> I'm using my named zone files from way back.
--- Amelia A Lewis wrote:
> $ORIGIN
>
> You haven't got one. You have a comment saying what the origin is,
> but no $ORIGIN directive in the example supplied.
Hi,
In my case replacing bootx64.efi with new one compiled with
aforementioned patch took off.
ODROID-H2 could boot kernel from latest snapshot.
Part of dmesg:
boot> boot bsd
booting hd0a:bsd: 14464328+3175440+344096+0+872448
[963989+128+1137408+860372]=0x14d15f0
entry point at 0x1001000
Hello,
I just upgraded one of my vmd virtual machine from OpenBSD 6.6 to 6.7 using
sysupgrade and noticed a new msyscall error message I have never seen before
during reboot as you can see below:
...
preserving editor files.
starting network daemons: sshd smtpd httpd.
starting package daemons:
Hi,
is there a possibility to install/boot OpenBSD in a Xen guest which is
booted by pvgrub1 or pvgrub2? The pvgrub is configured to use a
/boot/grub/grub.cfg of the guest in the 1st partition.
In a non-Xen-grub there is a bsd-module which can boot the installer
bsd.rd, but this bsd-module
On 2020-07-09, Matthew Weigel wrote:
> On 7/8/20 7:57 PM, Aisha Tammy wrote:
>> On dovecots side, I get:
>> Jul 8 20:28:59 mail dovecot: imap-login: Disconnected (no auth attempts in
>> 0 secs): user=<>, rip=98.109.25.191, lip=108.61.81.40, TLS handshaking:
>> SSL_accept()
>> failed:
On 2020-07-09, Aisha Tammy wrote:
> OK I found the error, the error is definitely something on our side of the
> port and not because of roundcube/dovecot
>
> When I turn peer verification off, roundcube is continues and establishes
> connection.
> I think that the reason for this is that
On 2020-07-09, Otto Moerbeek wrote:
> On Thu, Jul 09, 2020 at 01:19:47AM +, ken.hendrick...@l3harris.com wrote:
>
>> > server 127.0.0.1
>> Default server: 127.0.0.1
>> Address: 127.0.0.1#53
>> > set port 53053
> ^
>> > 172.24.20.1
>> Server: 127.0.0.1
>>
OK I found the error, the error is definitely something on our side of the port
and not because of roundcube/dovecot
When I turn peer verification off, roundcube is continues and establishes
connection.
I think that the reason for this is that roundcube needs to access the CA cert
files which
24 matches
Mail list logo
