On 2024-05-03, Harald Dunkel wrote:
> On 2024-05-02 21:25:00, Stuart Henderson wrote:
>>
>> You have an old fw_update(1) manual lying around which should be
>> removed. It moved to fw_update(8).
>>
>
> "Moved"?
Yes.
It used to be in section 1, it
On 2024-05-02 21:25:00, Stuart Henderson wrote:
You have an old fw_update(1) manual lying around which should be
removed. It moved to fw_update(8).
"Moved"?
And yet another BTW: https://man.openbsd.org/OpenBSD-7.5/ seems to
be forgotten.
Regards
Harri
On 2024-05-02, Harald Dunkel wrote:
> On 2024-04-30 13:25:39, Страхиња Радић wrote:
>> Дана 24/04/30 01:12PM, Kirill A. Korinsky написа:
>>> You may download it by hand and install as fw_update /path/to/firmware.tgz
>>
>> BTW, this is in fw_update(8).
>&
Дана 24/05/02 02:55PM, Harald Dunkel написа:
> SYNOPSIS
> fw_update [-adinv] [-p path] [driver ...]
>
> What is -F supposed to do? What happened to the -i?
I'm not sure what flavor are you using, but you should update it and
the packages (type ‘pkg_add
On Thu, May 02, 2024 at 02:55:33PM +0200, Harald Dunkel wrote:
> On 2024-04-30 13:25:39, ?? wrote:
> > 24/04/30 01:12PM, Kirill A. Korinsky :
> >> You may download it by hand and install as fw_update /path/to/firmwar
On 2024-04-30 13:25:39, Страхиња Радић wrote:
Дана 24/04/30 01:12PM, Kirill A. Korinsky написа:
You may download it by hand and install as fw_update /path/to/firmware.tgz
BTW, this is in fw_update(8).
man 8 fw_update
/SYNOPSIS
Another BTW:
# fw_update -i
fw_update
> How does fw_update install the drivers?
> How does it know which driver is missing on the system?
Just list the following sequence (outputs inserted too):
$ which fw_update
/usr/sbin/fw_update
$ cat /usr/sbin/fw_update
#!/bin/ksh
# $OpenBSD: fw_update.sh,v 1.56 2024/03/21 01:02:29 a
Дана 24/04/30 01:12PM, Kirill A. Korinsky написа:
> You may download it by hand and install as fw_update /path/to/firmware.tgz
BTW, this is in fw_update(8).
man 8 fw_update
/SYNOPSIS
On Tue, 30 Apr 2024 12:35:17 +0200,
fr...@lilo.org wrote:
>
> How does fw_update install the drivers?
It downloads firmware from http://firmware.openbsd.org/firmware/
and installs it as package in system.
> How does it know which driver is missing on the system?
It checks patterns
Hello,
Firmwares aren't drivers per say they are required along with the driver
Chris
Sent from Proton Mail Android
Original Message
On 4/30/24 5:35 AM, wrote:
> How does fw_update install the drivers?
> How does it know which driver is missing on the system?
How does fw_update install the drivers?
How does it know which driver is missing on the system?
All these questions to install the drivers manually (offline)
Tks
he
> > athn-firmware. I get it to work and now wanting to prep a USB disk
> > with all necessary firmware. I'm following the FAQ#4 on the website
> > (I suppose it works with more firmware than just the WiFi).
>
> fw_update does download and verify the signature on the S
essary firmware. I'm
> following the FAQ#4 on the website (I suppose it works with more firmware
> than just the WiFi).
>
> So, now to my question. Using fw_update -F to the current dir does download
> all firmware (5 files) and SHA256.sig. However, the file SHA256.sig does not
with more firmware than just the
WiFi).
So, now to my question. Using fw_update -F to the current dir does download all
firmware (5 files) and SHA256.sig. However, the file SHA256.sig does not
include the signature, using signify like so:
signify -Cp /etc/signify/openbsd-73-fw.pub -x SHA256.sig
Endeover:
In 7.3, I end up starting also unbound service by rcctl instead of
unbound-control (losing maybe something about security) hoping to give me a
better
general standard to control my services, including my approach
to sysupgrade.
Thanks to everyone who reply in the thread.
--
Thanks Steve.
Jul 30, 2023 00:07:35 Steve Litt :
> I use runit (on Void Linux) every day, and love it to death. Runit is
> extremely simple. S6 is a little more capable and a little more complex.
Thank you for all the hints, expecially about runit, I didn't know it.
I'm going trying to fix
Daniele B. said on Tue, 25 Jul 2023 16:33:50 +0200 (GMT+02:00)
>My unattended upgrade happend like that:
>
>- I took up unbound
>- sysupgrade
>- 1st fw_update (this probbly is okay)
>- reboot
>- installation of the sets
>- 2nd fw_update (this fails because unattende
On Jul 28, 2023 20:00:24 I was still sleeping when suddenly Paul said:
> If you really want to go without DNS resolution, I invite you to
> travel back a few decades and learn about /etc/hosts.
did you hear my
"True, the hosts.. Oh Jesus!"... ?
Many thx! :D
-- Daniele Bonini
I don't understand - if you configure your system to not have working
DNS resolution, then you will not have working DNS resolution.
fw_update needs working DNS resolution, so yeah .. if you break the
latter, you break the former.
Don't break DNS resolution. You really get what you pay
My unattended upgrade happend like that:
- I took up unbound
- sysupgrade
- 1st fw_update (this probbly is okay)
- reboot
- installation of the sets
- 2nd fw_update (this fails because unattended, local Unbound is down)
- reboot
- 3rd fw_update (this fails because unattended, local Unbound
sounds like if unbound started before
> fw_update, there would be no problem
I also would like the possibility to rewind my mindset to two years ago to have
the proper
technical answer when I need it.. However I try to answer you..
Basically I think while experimenting I found interesting the possi
-i resolv.conf && echo nameserver 8.8.8.8 >> resolv.conf && chattr +i
resolv.conf
I also don't understand why you start unbound manually instead of from
computer initialization. It sounds like if unbound started before
fw_update, there would be no problem.
SteveT
Steve Litt
penBSD 7.3 and thanks again for
>> it.. ;)
>>
>> No particular problem except my realization that with my settings
>> (unbound started manually) fw_update goes to fail (all the three
>> attempts) on each (unattended) upgrade. If fw_update happens to be a
>> co
On 2023-07-25, Daniele B. wrote:
>
> Hello,
>
> Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
> it.. ;)
>
> No particular problem except my realization that with my settings
> (unbound started manually) fw_update goes to fail (all the three
> at
Hello,
Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
it.. ;)
No particular problem except my realization that with my settings
(unbound started manually) fw_update goes to fail (all the three
attempts) on each (unattended) upgrade. If fw_update happens
Andrew Hewus Fresh writes:
> On Sun, Dec 11, 2022 at 08:06:24PM -0500, Rob Whitlock wrote:
> > On line 408, fw_update has the expression ${LOCALSRC:#file:}. The parameter
> > substitution ${name:#word} is not documented in the manual page for ksh yet
> > its behavior s
On Sun, Dec 11, 2022 at 08:06:24PM -0500, Rob Whitlock wrote:
> On line 408, fw_update has the expression ${LOCALSRC:#file:}. The parameter
> substitution ${name:#word} is not documented in the manual page for ksh yet
> its behavior seems to be equivalent to ${LOCALSRC#file:}.
On Sun, Dec 11, 2022 at 08:06:24PM -0500, Rob Whitlock wrote:
> On line 408, fw_update has the expression ${LOCALSRC:#file:}. The parameter
> substitution ${name:#word} is not documented in the manual page for ksh yet
> its behavior seems to be equivalent to ${LOCALSRC#file:}.
On line 408, fw_update has the expression ${LOCALSRC:#file:}. The parameter
substitution ${name:#word} is not documented in the manual page for ksh yet
its behavior seems to be equivalent to ${LOCALSRC#file:}. Assuming this is
a typo, a patch is provided to remove the colon. If it is not a typo
Hi Ingo,
On 2021/12/26 23:26, Ingo Schwarze wrote:
> Hi Alexander,
>
> Alexander wrote on Sun, Dec 26, 2021 at 08:11:51PM +:
> > On 2021/12/25 18:02, Ingo Schwarze wrote:
>
> >> The new fw_update shell script is not in CVS yet.
> >>
> >> Thi
Hi Alexander,
Alexander wrote on Sun, Dec 26, 2021 at 08:11:51PM +:
> On 2021/12/25 18:02, Ingo Schwarze wrote:
>> The new fw_update shell script is not in CVS yet.
>>
>> This command provides a clue that could lead you to suspect the above:
>>
>>$ gr
Thank you everyone for the helpful and detailed explanations!
On 2021/12/25 18:02, Ingo Schwarze wrote:
> The new fw_update shell script is not in CVS yet.
>
> This command provides a clue that could lead you to suspect the above:
>
>$ grep -m 1 OpenBSD $(which fw_update)
&
Hi Alexander,
Alexander wrote on Sat, Dec 25, 2021 at 04:07:07PM +:
> I just wanted to check for new firmware versions:
>
> $ fw_update -n
> fw_update: unknown option -- -n
> usage: fw_update [-d | -D] [-av] [-p path] [driver | file ...]
>
> This used to work
/us
fw_update is being replaced with a new program, and this is being tested
in snapshots to ensure we have coverage all all circumstances.
The new program is capable of updating firmwares while in the bsd.rd
install/upgrade phase. This means some firmwares (specially *drm firmwares)
will get
On Sat, Dec 25, 2021 at 04:07:07PM +, Alexander wrote:
> at https://cvsweb.openbsd.org/src/usr.sbin/fw_update/ which has been in
> the attic for the last 6 years.
> Where do I actually find the version history of the fw_update that is
> installed on my system in CVSweb?
fw_upda
Hi all,
I just wanted to check for new firmware versions:
$ fw_update -n
fw_update: unknown option -- -n
usage: fw_update [-d | -D] [-av] [-p path] [driver | file ...]
This used to work and is still documented like this in
$ man 8 fw_update
[...]
-n Dry run. Do not actually install
Old snapshot working fine at first run, installing all fw_update needed
packages:
Build date: 1635104269 - Sun Oct 24 19:37:49 UTC 2021
Last snapshot, stuck at fw_update, not installing. Using manual fw_update
works fine after that.
Build date: 1635178887 - Mon Oct 25 16:21:27 UTC 2021
After
On 2021-04-08, Luke Small wrote:
> I make unbound connect to dnscrypt-proxy and after an update, it’ll just
> sit there for what seems like 2 minutes while fw_update inevitably fails
> before turning on dnscrypt-proxy. I’ve been running snapshots and that’s
> really dumb. Or is
On Thu, Apr 08, 2021 at 01:50:59PM -0500, Luke Small wrote:
> I make unbound connect to dnscrypt-proxy and after an update, it’ll just
> sit there for what seems like 2 minutes while fw_update inevitably fails
> before turning on dnscrypt-proxy. I’ve been running snapshots and that’s
>
I make unbound connect to dnscrypt-proxy and after an update, it’ll just
sit there for what seems like 2 minutes while fw_update inevitably fails
before turning on dnscrypt-proxy. I’ve been running snapshots and that’s
really dumb. Or is there a way to have unbound connect to a failover server
‐‐‐ Original Message ‐‐‐
On Wednesday, July 15, 2020 12:49 PM, Theo Buehler wrote:
> One server had an incorrect config. This should be fixed now.
Thanks for your notification, so I didn't go mad ;) I can confirm, it works
like a charm. Thanks again for fixing!
On Tue, Jul 14, 2020 at 07:57:35PM +, mabi wrote:
> Hello,
>
> I just updated from 6.6 to 6.7 and the fw_update part failed so I tried to
> run it manually and get:
>
> $ sudo fw_update -n
> http://firmware.openbsd.org/firmware/6.7/: no such dir
> Couldn't find up
On 15/7/20 5:57 am, mabi wrote:
> http://firmware.openbsd.org/firmware/6.7/: no such dir
> Couldn't find updates for intel-firmware-20191115v0
>
> It looks like I have a colon ":" at the end of the URL which of course makes
> the URL invalid. Now how could this happen? and in which file do I fix
Hello,
I just updated from 6.6 to 6.7 and the fw_update part failed so I tried to run
it manually and get:
$ sudo fw_update -n
http://firmware.openbsd.org/firmware/6.7/: no such dir
Couldn't find updates for intel-firmware-20191115v0
It looks like I have a colon ":" at the end of the
> This has nothing to do with OpenBSD.
If OpenBSD would have a switch to disable usage of all BLOBs provided by OBSD
at once on an user desire.
Does OpenBSD have any other BLOBs except firmwares which can be
deleted/renamed/moved?
> Please read your own statement. You aren't qualified
ode 6: Return of the Vendor:
> http://marc.info/?l=openbsd-misc=128779369427908=2
NO.
it is completely UNRELATED to the subject which is about fw_update
fw_update does NOT update controller firmware on that device.
On Fri, May 15, 2020 at 3:39 AM Nick Holland
wrote:
>
> On 2020-05-14 11:08, i...@aulix.com wrote:
>
> I actually had Adaptec give me a firmware update with a time bomb in
> it, and didn't bother to tell me that after X days, it would brick my
> adapter and prevent me from updating/downdating it.
On Thu, May 14, 2020 at 04:25:11AM +, 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 installing?
Others pointed out that firmwares are signed.
Fo
Nick Holland wrote:
> On 2020-05-14 11:08, i...@aulix.com wrote:
> >> If that binary code was on a ROM, would it be less malicious?
> >
> > Cannot more recent and up to date binary code be more malicious than
> > old one in the ROM?
>
> This has nothing to do with OpenBSD. That can be true
On 2020-05-14 11:08, i...@aulix.com wrote:
>> If that binary code was on a ROM, would it be less malicious?
>
> Cannot more recent and up to date binary code be more malicious than
> old one in the ROM?
This has nothing to do with OpenBSD. That can be true for any kind of
code update, whether
i...@aulix.com wrote:
> > If that binary code was on a ROM, would it be less malicious?
>
> Cannot more recent and up to date binary code be more malicious than old one
> in the ROM?
Our firmwares do not replace code on ROM, since the hardware in question
HAS NO ROM.
> If that binary code was on a ROM, would it be less malicious?
Cannot more recent and up to date binary code be more malicious than old one in
the ROM?
Just because backdoor development is progressing as time goes and old backdoors
may be less dangerous compared to modern ones?
> If the
Janne Johansson wrote:
> Den tors 14 maj 2020 kl 06:27 skrev Mogens Jensen <
> mogens-jen...@protonmail.com>:
>
> > Normally I would just assume that fetched files are verified, but maybe
> > in the case with fw_update, the rationale is that firmware files are
> &
On 2020-05-14, 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 installing?
>
> There is a SHA256.sig in the remote firmware directory, but no
&g
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 installing?
There is a SHA256.sig in the remote firmware directory, but no
indication from fw_update, even with verbose output
Den tors 14 maj 2020 kl 06:27 skrev Mogens Jensen <
mogens-jen...@protonmail.com>:
> Normally I would just assume that fetched files are verified, but maybe
> in the case with fw_update, the rationale is that firmware files are
> binary blobs so we can't know if they are m
The firmwares are packages, and are signed with the
/etc/signify/openbsd-XX-fs.pub key.
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 fil
. Whatever
new other storage location we select, it won't contain the files you need,
because you would not have copied the entire pile of firmwares to that place.
I do have a mirror of firmware.openbsd.org and it works if I specify the
location with fw_update -p http://mymirror.lol/openbsd/firmware/6.6
Tommy Nevtelen [to...@nevtelen.com] wrote:
> Hi!
>
> I have some systems without access to the Internets and with internal
> mirrors for packages and fw_update packages. But when openbsd does a
> sysupgrade or a new install it runs fw_update against firmware.openbsd.org.
>
Tommy Nevtelen wrote:
> I have some systems without access to the Internets and with internal
> mirrors for packages and fw_update packages. But when openbsd does a
> sysupgrade or a new install it runs fw_update against
> firmware.openbsd.org. The problem here is that it wil
Tommy Nevtelen wrote:
> I have some systems without access to the Internets and with internal
> mirrors for packages and fw_update packages. But when openbsd does a
> sysupgrade or a new install it runs fw_update against
> firmware.openbsd.org. The problem here is that it wil
Hi!
I have some systems without access to the Internets and with internal
mirrors for packages and fw_update packages. But when openbsd does a
sysupgrade or a new install it runs fw_update against
firmware.openbsd.org. The problem here is that it will hang until the
timeout is reached
In the latest mds errata patch, I noticed that one of the steps is to
run fw_update. From briefly looking over the syspatch script, I don't
see it calling fw_update once a patch is applied.
Would you welcome a diff to add support for this? If so I can look at
writing one. It would check
-Original Message-
From: Theodore Wynnychenko
Sent: Wednesday, November 01, 2017 8:43 AM
To: misc@openbsd.org
Subject: fw_update signify unsigned package on current and 6.2-stable
Hello:
How do I install the iwm-firmware without a network connection on either
6.2-stable
drive with the "iwm-firmware-0.20170105.tgz" on it, and issued:
# fw_update -p /mnt iwm
This worked a couple of months ago, and the wireless came up. Yesterday (and
today), I got/get:
file:/mnt/iwm-firmware-0.20170105.tgz: unsigned package (signify(1) doesn't see
old-style signatures)
I se
On Tue, Oct 04, 2016 at 03:15:18PM +0200, Marc Espie wrote:
> - the new scheme is slightly more unflexible with respect to unsigned
> data: by default, every .tgz is piped thru signify -Zs, so
> pkg_add/pkg_info/fw_update WON'T even see any data if it's not signed.
> Err
d the only thing that sees them is signify -Zs.
pkg_add/fw_update only ever sees "safe" input, so that all the data
that will be gunzip'd/untared is already checked.
This has some rough edges.
- old snapshots will not see the new signatures at all (this is still
a gzip archive with tra
On 2016-10-03 14:11, Mihai Popescu wrote:
I've installed a snapshot somewhile ago, then I needed to update the
firmware for athn device. I get this error:
# fw_update
UNSIGNED PACKAGES: athn-firmware-1.1p1
Fatal error: Unsigned package
http://firmware.openbsd.org/firmware/snapshots/athn
I've installed a snapshot somewhile ago, then I needed to update the
firmware for athn device. I get this error:
# fw_update
UNSIGNED PACKAGES: athn-firmware-1.1p1
Fatal error: Unsigned package
http://firmware.openbsd.org/firmware/snapshots/athn-firmware-1.1p1.tgz
at /usr/libdata/perl5/OpenBSD
Hello,
The path for firmware files used by fw_update needs to be updated for 5.4,
otherwise a manual install is necesary.
Thank you.
Please elaborate.
I'm sorry for the quick suggestion. Here are the details...
I was installing from snapshots and the fw_update was run at first boot. I
was using bge0 for network connection in a hope that the firmware for iwi0
will be installed. I got a message, then when I was trying to use
On 07/19/13 18:01, Mihai Popescu wrote:
Hello,
The path for firmware files used by fw_update needs to be updated for 5.4,
otherwise a manual install is necesary.
Thank you.
Are you suggesting there are more non-free firmwares that we don't
automagically fetch? Please elaborate.
On 07/19/13 19:22, Mihai Popescu wrote:
Please elaborate.
I'm sorry for the quick suggestion. Here are the details...
I was installing from snapshots and the fw_update was run at first boot. I
was using bge0 for network connection in a hope that the firmware for iwi0
will be installed. I got
-of-topic comments. I think I was in evangelic mode.. Sorry.
Last question. Which is the best way to disable fw_update so that when it
connects to the network it doesnB4t attempt to install more firmware? Stuart
suggested:
# echo 127.0.0.1 firmware.openbsd.org /etc/hosts
will this work if I have
* David Coppa dco...@gmail.com [2012-05-09 23:40]:
If you have concerns with firmwares, swap your card with, for example, an
atheros or another card that doesn't need a firmware.
wait.
on those cards, the firmware is simply on the card itself, usually in
some kind of flash.
where's the
If you're really *that* worried you should build everything you use from
source after trawling through the source.
Personally I'd be much more concerned about all the other components on
your internet connection from router to ISP.
Then of course there's your mobile phone...
On May 9,
On Thu, May 10, 2012 at 2:34 AM, Brett brett.ma...@gmx.com wrote:
I would like to hear your arguments on this and if there is a simple way to
disable fw_update and uninstall in general everything propietary
affecting the network card that I have not been warned about.
If you're using a PC you
On Thu, 10 May 2012 00:46:05 +0200
Alexander Hall wrote:
revision 1.654
date: 2011/11/08 19:55:52; author: deraadt; state: Exp; lines: +2 -6
Now that the code is well tested, don't ask the firmware question
anymore. Saves 141 precious bytes on the inside of the media.
ok krw
I bet he
If you have concerns with firmwares, swap your card with, for example, an
atheros or another card that doesn't need a firmware.
Some atheros does use firmware, eg athn(4).
Not all the athns. Only USB ones, like the AR9271, need a firmware.
Mine is an Atheros (athn, I don't know the model now
On Thu, May 10, 2012 at 12:03 PM, mark sullivan mark.sulli...@gmx.fr wrote:
I didn't even have the chance to test if it would work without it.
Yes, it should work.
Just remove the package with pkg_delete athn-firmware.
My advice is to not use a computer at all.
Stick to pen and paper.
P.S. You are a fucking stupid fucking moron.
I would suggest that you fashion a hat
out of aluminum foil and wear it firmly
on your head. This way you will stop
wasting the time of rational people.
On Thu, May
Also, while I recognize this is an edge case, I have in the past sold
systems with OpenBSD installed on them to other people, and now that I
come to think of it I have no idea whether that's legal to do with, say,
iwn-firmware installed on it (it's probably not).
Every firmware package includes a
On Thu, May 10, 2012 at 10:34:14AM +1000, Brett wrote:
Easiest way to disable the uvideo firmware (and any bios video spyware) is to
stick black electrical tape over the webcam lens.
When I was a kid, one of the science experiments we did was to use a
speaker as a microphone.
Electrical
On Wed, May 9, 2012 at 3:33 PM, mark sullivan mark.sulli...@gmx.fr wrote:
I would like to hear your arguments on this and if there is a simple way
to disable fw_update and uninstall in general everything propietary
affecting the network card that I have not been warned about. I read
Hi everybody,
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I install
it (amd64 flavour), I see that fw_update automatically installs propietary
firmware without my permission. Actually even worse, it updates it
automatically from the net!
The parts affected are quite
On 05/09/12 21:33, mark sullivan wrote:
Hi everybody,
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I install
it (amd64 flavour), I see that fw_update automatically installs propietary
firmware without my permission. Actually even worse, it updates it
automatically
and when I
install it (amd64 flavour), I see that fw_update automatically installs
propietary firmware without my permission. Actually even worse, it updates
it automatically from the net!
The parts affected are quite meaningful: the network card and the video
card... I mean.. Should I
On Wed, May 09, 2012 at 21:33, mark sullivan wrote:
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I
install it (amd64 flavour), I see that fw_update automatically installs
propietary firmware without my permission. Actually even worse, it updates
it automatically from
Il giorno 09/mag/2012 21:38, mark sullivan mark.sulli...@gmx.fr ha
scritto:
Hi everybody,
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I
install it (amd64 flavour), I see that fw_update automatically installs
propietary firmware without my permission. Actually even worse
that fw_update automatically installs
propietary firmware without my permission. Actually even worse, it updates
it automatically from the net!
The parts affected are quite meaningful: the network card and the video
card... I mean.. Should I request that you install propietary firmware
for my
On 2012-05-09, mark sullivan mark.sulli...@gmx.fr wrote:
I would like to hear your arguments on this and if there is a
simple way to disable fw_update and uninstall in general everything
propietary affecting the network card that I have not been warned
about.
In the cases of the firmware
I would like to hear your arguments on this and if there is a simple way to
disable fw_update and uninstall in general everything propietary
affecting the network card that I have not been warned about.
If you're using a PC you should probably also be aware that
there is likely to be bios
On Thu, May 10, 2012 at 10:34, Brett wrote:
You can use pf to block those network devices that have firmware you don't
trust
Way too late at that point. It's already copied your top zecret data to the
NSA.
On Thu, 10 May 2012 00:55:07 +
Ted Unangst t...@tedunangst.com wrote:
On Thu, May 10, 2012 at 10:34, Brett wrote:
You can use pf to block those network devices that have firmware you don't
trust
Way too late at that point. It's already copied your top zecret data to the
NSA.
On Wed, 2012-05-09 at 21:33 +0200, mark sullivan wrote:
Hi everybody,
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I
install it (amd64 flavour), I see that fw_update automatically installs
propietary firmware without my permission. Actually even worse, it updates
it was because
fw_update might be buggy.
Also, while I recognize this is an edge case, I have in the past sold
systems with OpenBSD installed on them to other people, and now that I
come to think of it I have no idea whether that's legal to do with, say,
iwn-firmware installed on it (it's probably
, mark sullivan wrote:
Hi everybody,
I was coming to OpenBSD 5.1 looking for reasonable privacy and when I
install it (amd64 flavour), I see that fw_update automatically installs
propietary firmware without my permission. Actually even worse, it
updates
it automatically from the net
97 matches
Mail list logo
