The firmwares are packages, and are signed with the
There is no risk.
Mogens Jensen wrote:
> I was just trying out the fw_update program on OpenBSD 6.5, deleting/
> installing all the firmware and was wondering if fw_update will verify
> the files before
Sorry for late reply but I had a problem accessing this device.
I’ve tried both OpenBSD 6.6 and 6.7 (amd64), nothing changed:
I think you’re probably right; transceiver command is only available for
But what about ifconfig em0 media output showing only supporting
On 13/05/2020 13:10, mabi wrote:
> I am currently running OpenBSD 6.5 as firewall with two ix interfaces inside
> a trunk interface with LACP protocol. On top of that I have a few vlan
> interfaces so it's basically (ix -> trunk -> vlan).
> Now I saw that OpenBSD has a new interface
Kevin Chadwick wrote:
> The unveil man page is perfectly correct and it is not hard to test it's
> I just wonder if it may aid unveil adoption in languages other than C, if it
> explicitly mentioned that exec is not required on a dir to allow reading the
> files within, e.g. if
The unveil man page is perfectly correct and it is not hard to test it's
I just wonder if it may aid unveil adoption in languages other than C, if it
explicitly mentioned that exec is not required on a dir to allow reading the
files within, e.g. if the dev is more used to filesystem
On Tue, May 12, 2020 at 11:46:58AM -0300, Fabio Martins wrote:
> I believe loongson people are primaly after running some Linux distros for
> their processor (new ones), but maybe if you ask them directly about their
> plans to donate people's effort / hardware to OpenBSD, might be a good
I am currently running OpenBSD 6.5 as firewall with two ix interfaces inside a
trunk interface with LACP protocol. On top of that I have a few vlan interfaces
so it's basically (ix -> trunk -> vlan).
Now I saw that OpenBSD has a new interface specifically for LACP which is
On 2020-05-13 11:02, i...@aulix.com wrote:
(all your emails to @misc)
the best way to get answers to all of your questions regarding OpenBSD
is to try and run OpenBSD for a few years trying to make it help with
your real-world needs, such as personal laptop, home gateway,
> This is "testing the waters" racism.
Where did you find an indication of a racism?
Btw, thanks for this site link, may be something like:
> On Wed, May 13, 2020 at 12:59:26PM +0200, i...@aulix.com wrote:
>> Thanks for your suggestion,
>> but googling for keys:
On Tue, May 12, 2020 at 05:09:16AM +0200, i...@aulix.com wrote:
> Treat it as my secret, I want and that is why I ask because I can, I wish you
> tell me the answer without a knowledge of "why I ask",
> it is a very long discussion of answering by a question to question in your
> Jewish style,
Thanks for suggestion, I already have seen it and even contacted SSH developer
Damien Miller regarding FIDO key support a few weeks ago.
What I am looking for right now is something different, it is if
ssh-pkcs11-helper works with SSHD daemon on OpenBSD to store there its server
private key in
On Wed, May 13, 2020 at 12:59:26PM +0200, i...@aulix.com wrote:
> Thanks for your suggestion,
> but googling for keys: +openbsd +nitrokey
> does not indicate anything interesting except a few of my own questions on
> the Nitrokey support forum.
I had to look up "Nitrokey" to verify that
since rpki-client has its own home page like other "associated projects",
it makes sense to add a new link.
RCS file: /cvs/www/index.html,v
retrieving revision 1.740
diff -u -p -r1.740
Thanks for your suggestion,
but googling for keys: +openbsd +nitrokey
does not indicate anything interesting except a few of my own questions on the
Nitrokey support forum.
I would like to hear from some real OpenBSD user about he is happy with
Nitrokey on OpenBSD.
Another my point is about
> Free advice from a fellow East European who might better understand
your obnoxious behaviour on this list:
I find behavior of commenters like you much more obnoxious and simply trolling
me and the whole topic of this thread and some interesting facts mentioned here
which might not please
So I've confirmed that sd_get_parms is returning -1 here (by using
printf() statements in /usr/src/sys/scsi/sd.c):
1671: if (sd_read_cap(sc, flags) != 0)
Then then sets this error variable to -1:
218: error = sd_get_parms(sc, sd_autoconf);
Then this check is false, and
Mail list logo