My main memory is the rPi imager also allowed headless Wifi set up,
which had not be possible/easy previously. I can't remember if it worked?
Pancho <Pancho.Jones@proton.me> wrote:
My main memory is the rPi imager also allowed headless Wifi set up,
which had not be possible/easy previously. I can't remember if it worked?
WiFi is/was configured in wpa_supplicant.txt, and that worked fine
without the RPi imager program.
On 28/01/2025 06:14, Computer Nerd Kev wrote:
Pancho <Pancho.Jones@proton.me> wrote:Was...
My main memory is the rPi imager also allowed headless Wifi set up,
which had not be possible/easy previously. I can't remember if it
worked?
WiFi is/was configured in wpa_supplicant.txt, and that worked fine
without the RPi imager program.
All change with bookworm IIRC
On 28/01/2025 08:51, The Natural Philosopher wrote:
On 28/01/2025 06:14, Computer Nerd Kev wrote:
Pancho <Pancho.Jones@proton.me> wrote:Was...
My main memory is the rPi imager also allowed headless Wifi set up,
which had not be possible/easy previously. I can't remember if it
worked?
WiFi is/was configured in wpa_supplicant.txt, and that worked fine
without the RPi imager program.
All change with bookworm IIRC
UK law: Product Security and Telecommunications Security Act 2022 which
is amongst things, designed to stop devices, like routers for example,
from having default passwords that can easily be guessed. That's because
many people leave the passwords at the default settings and then such
devices are more easily roped into DDOS attacks.
I can offer some suggestions: use version 1.85 of the Imager program.
It has solved some of the password entry issues of the older version.
Also it allows you to use a different user name than pi, but I like pi
so I use it. Use the latest Raspberry Pi OS, either 64 or 32 bit as appropriate.
Is there **really** such a big security issue with default login names
and passwords on Raspberry Pis? Surely almost all of them are going
to be on home networks behind NAT routers and also surely no one is
going to (without thinking about it a bit!) put confidential data on
one. Anyone installing any system which is going to be directly out
on the internet should be very aware of the risks and will do what's required.
On 2025-01-26, Chris Green <cl@isbd.net> wrote:
Is there **really** such a big security issue with default login names
and passwords on Raspberry Pis? Surely almost all of them are going
to be on home networks behind NAT routers and also surely no one is
going to (without thinking about it a bit!) put confidential data on
one. Anyone installing any system which is going to be directly out
on the internet should be very aware of the risks and will do what's
required.
Probably not. People installing special-purpose distributions (media
player, dns filtering, hoem automazion etc.) may not even be aware that they need to change the SSH password when they only interact with some web frontend.
Also, it is not just the data on the device that is at risk. There is also the risk that such an exposed machine will be used as part of a botnet to attack other machines.
A quick check on shodan shows 86362 hits for "ssh raspbian". If only a small percentage of these use the default password, that is way too much.
cu
Michael
A quick check on shodan shows 86362 hits for "ssh raspbian". If only a small >> percentage of these use the default password, that is way too much.But ssh is not enabled by default in Raspbian.
mm0fmf <none@invalid.com> wrote:
On 28/01/2025 08:51, The Natural Philosopher wrote:
On 28/01/2025 06:14, Computer Nerd Kev wrote:
Pancho <Pancho.Jones@proton.me> wrote:Was...
My main memory is the rPi imager also allowed headless Wifi set up,
which had not be possible/easy previously. I can't remember if it
worked?
WiFi is/was configured in wpa_supplicant.txt, and that worked fine
without the RPi imager program.
All change with bookworm IIRC
UK law: Product Security and Telecommunications Security Act 2022 which
is amongst things, designed to stop devices, like routers for example,
from having default passwords that can easily be guessed. That's because
many people leave the passwords at the default settings and then such
devices are more easily roped into DDOS attacks.
Also the California Senate Bill 327:
"(b) Subject to all of the requirements of subdivision (a), if a connected device is equipped with a means for authentication outside a local area network, it shall be deemed a reasonable security feature under subdivision (a) if either of the following requirements are met:
(1) The preprogrammed password is unique to each device manufactured.
(2) The device contains a security feature that requires a user to generate
a new means of authentication before access is granted to the device for the first time. "
https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180SB327
On 28/01/2025 06:14, Computer Nerd Kev wrote:
Pancho <Pancho.Jones@proton.me> wrote:Was...
My main memory is the rPi imager also allowed headless Wifi set up,WiFi is/was configured in wpa_supplicant.txt, and that worked fine
which had not be possible/easy previously. I can't remember if it worked? >>
without the RPi imager program.
All change with bookworm IIRC
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 28/01/2025 06:14, Computer Nerd Kev wrote:
Pancho <Pancho.Jones@proton.me> wrote:Was...
My main memory is the rPi imager also allowed headless Wifi set up,WiFi is/was configured in wpa_supplicant.txt, and that worked fine
which had not be possible/easy previously. I can't remember if it worked? >>>
without the RPi imager program.
All change with bookworm IIRC
Sounds like I got off the RPiOS ship just at the right time before
they went completely nuts. Choice of distros is such a wonderful
advantage of Linux (even if there's less choice for the Pis than
for PC).
Well I stick to PIOS simple because it is the documented standard.
Networking is handled by the Network Manager and it gets tricky to set
that up without a console screen/keyboard at least - but there is a
great utility called nmcli I think that 'does everything' once you have learnt its magic spells.
To be honest although it is possible to do everything over ssh, the
chances of losing connectivity while messing with the network are high
and a HDMI screen and a USB keyboard are not hard to rig up with the appropiate adapters.
Well I stick to PIOS simple because it is the documented standard.
Networking is handled by the Network Manager and it gets tricky to set
that up without a console screen/keyboard at least - but there is a
great utility called nmcli I think that 'does everything' once you have >learnt its magic spells.
In article <vnbqo3$21n98$4@dont-email.me>,
The Natural Philosopher <tnp@invalid.invalid> wrote:
Well I stick to PIOS simple because it is the documented standard.
Networking is handled by the Network Manager and it gets tricky to set
that up without a console screen/keyboard at least - but there is a
great utility called nmcli I think that 'does everything' once you have
learnt its magic spells.
There's also nmtui, which works in the same places nmcli does, but is much easier to navigate.
On 29/01/2025 21:14, Scott Alfter wrote:
In article <vnbqo3$21n98$4@dont-email.me>,Indeed yes. Does it cover all the options? I never got around to using
The Natural Philosopher <tnp@invalid.invalid> wrote:
Well I stick to PIOS simple because it is the documented standard.
Networking is handled by the Network Manager and it gets tricky to set
that up without a console screen/keyboard at least - but there is a
great utility called nmcli I think that 'does everything' once you have
learnt its magic spells.
There's also nmtui, which works in the same places nmcli does, but is much >> easier to navigate.
it. My configuration was nicely handled by nmcli...
On 2025-01-26, Chris Green <cl@isbd.net> wrote:
Also, it is not just the data on the device that is at risk. There is also the risk that such an exposed machine will be used as part of a botnet to attack other machines.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 502 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 211:22:43 |
| Calls: | 9,878 |
| Calls today: | 6 |
| Files: | 13,791 |
| Messages: | 6,205,117 |