Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
What if you really hate the fact that The RPi foundation is being hostile against people nowadays with proprietary PCIe connectors, telemetry, requiring a custom flash tool to get SSH and whatnot?
You can dd the iso without any problems.
Yes you can, but then without a display and keyboard you won't be able to SSH into the thing right away. They're using small tricks like that to push people into their tool and you'll be seeing more of that crap in the future.
Don't you just touch SSH in the /boot dir after you flash, then you can SSH in as pi and password raspberry?
The workarounds are either using their tool or doing what you suggested. Other SBCs do the reasonable thing and have it enabled by default like the Pi did in the past. This change simply pushes less-proficient users into using their tool.
Having it enabled by default is a pretty massive security hole. I preordered the raspberry pi 1 when it launched and I don’t remember SSH ever being enabled be default in their images. Where did you hear it was enabled by default?
I was, I remember it being that way. They later on made it so you would be required to change the password after the first login.
Most people are running those in a home network that is isolated either way. Most people even share their entire hard drives on the network with little to no security and you're telling me a Pi with SSH access enabled by default is a risk? Professional deployments will be done by people who know how to change the passwords, port and use keys. There's no reason to consider that an issue because of those reasons.
That’s just good password security and reasonable.
See that qualifying word there? “Most”? That’s why they force SSH to be disabled and password changes. If you PERSONALLY can guarantee that no one will EVER put a freshly imaged RPi directly on the internet backed by a 10 million dollar/pound/euro guarantee per incident it still doesn’t matter; there’s still a need to change these defaults. I’ve seen the RPi’s deployed in a business environment and I 10000% know that vendors are fscking stupid and would leave default permissions enabled because they’re the lowest bidder.
It’s people like you why we have massive botnets due to default security measures being ignored by major manufacturers.
Good day sir.
Case in point: a number of years ago I knew a kid who was smart enough to flash Tomato on his router, enable SSH and even install a bunch of Entware packages. But he wasn't intelligent enough to change the SSH port from 22 or leave the remote access disabled.
Fast forward a month or two and his ISP tells him that they traced some pretty serious botnet shenanigans to his IP.
Just because someone is smart enough to use a device doesn't necessarily mean they're intelligent enough to use it safely.
Yes, that's my point, you don't need to disable it by default.
There are those things called licenses and liability liability waivers that are signed specially for those cases. The people doing deployments on business environment should know how to change password / use SSH keys and whatnot, if they don't that's not the Pi's problem.
By enabling people who shouldn't be configuring Pi boards in the first place you're are the one creating botnets. They might be saved by the fact that it doesn't have SSH enabled by default just to be hacked later on when they decide to run a
sudo wget ... | sh.Making things easier has this downside, you protect people so much, they don't ever learn and then things go bad they can't handle it and the damage is way way worse.
Now you’re just a troll arguing in bad faith.
I SAID GOOD DAY SIR!
This is not true
https://roboticsbackend.com/enable-ssh-on-raspberry-pi-raspbian/
The workarounds are either using their tool and/or fiddling on the SD card. Other SBCs do the reasonable thing and have it enabled by default. This simply pushes people into using their tool.
The extra menu in the flasher does the magic on the sd-card. I’ve been setting up headless pi’s since before 3b came out, and the same options are available today.
The idea that ssh being enabled by default is reasonable is just like your opinion. Did you know you have to enable it during installation on both Debian and canonicals derivative? Maybe it’s still on by default on fedora (with root login enabled to help you!)
If editing your config is fiddling then I struggle to see your use of an sbc.
The difference is that Debian requires you to install with a screen/keyboard and/or use something generic like cloud-init not a proprietary tool that pushes people into telemetry and whatnot. Also a Pi is a lot less critical than a full system and almost always used by hobbyists. Professional users would change passwords / use keys so, yes, it makes absolutely no sense.
The Debian installer can be pre-seeded and be automated. You can use cloud-init for non cloud installs but why would you? Preseed or use fai and let your config system handle the rest.
I get that you love this board and think that “the establishment” is evil. But you come off as someone not having the knowledge to back your assumptions.
Sometimes this will be the right board, sometimes a Pi is better. And sometimes 2-3 microcontrollers are a better fit. But the choice should not be based on telemetry in an optional imager, or the fact that your headless setup requires editing of config files.
No, no. I like “the establishment” as long as it doesn't turn out to end up like Google Chrome. Think about it, few things against the Pi:
Overall the Pi is isn't even great at anything specific besides "holding the hand" of beginners and whatnot. If you're looking for a networking / storage solution you're better using another SBC with real PCI and/or a Mini PC. If you're into electronics an ESP32 will be more than enough to drive a couple of GPIOs and will cost 3$, in short too little CPU for computing tasks and too much CPU for basic electronics. If you're under heavy industrial environments the Pi won't be up to your certifications or you'll require protective gear that is so expensive that a solution from Gateworks will be cheaper at that point.
On a side note, just notice how the Pi bulldozed the Arduino business by simply integrating the GPIO in the CPU and then now they're going in the opposite direction into the classic "big CPU talks to small microcontroller architecture for low level stuff" with their "innovative" RP1 chip.
...and I'm not the only person with that 1 2 opinion it seems.
I do agree with you there, I know the the Pi is better in education, hobbyists and people who aren't that proficient with electronics and computers however it opens the door to a lot of potencial market abuse, Apple-style and whatnot. At the end of the day it is overpriced and it isn't really good at anything - not even in ethics - as specialized options in those niches (ESP32, Arduino, Other SBCs, MiniPCs...) are better for said use cases.
It looks a lot like the Pi Foundation knows about this market-fit issue and is just trying to push more and more stuff into the hobbits as a way to keep growing and making money. The SSH/telemetry/app bundle thing isn't objectively bad alone, but people aren't complaining and it is just opening the door to a LOT of more custom stuff and eventually a closer ecosystem and a situation like Chrome market dominance.
What the next step for them? A cloud service that you need to use / pay to develop stuff for the Pi? :)
How is a pi (or other single-board computers) less critical than “a full system”? Do you have any idea how many pi’s are out there running serious stuff? Where I work I bump into them all over - including in security systems and door-access.
This one has two 2.5gb ports, 8 to 32gb ram. This is serious stuff for an sbc, clearly overkill for your pihole install. What’s not equally serious with banana pi is support. I went to their wiki, it lists Android and Debian (previous version) “images” but no download links, so it’s hard for me to verify that this board boots with sshd running or not. Like I said Debian does not, and for a good reason. Raspberry pi os pulls from raspbian, and they pull from Debian.
You can run Ubuntu LTS, fedora or others on your pi.
The telemetry is bad news - soon we will be out of food because someone knows what size of sd-cards you use, and the number of installs you do. So better go buys a silly board, track down some ancient image of an install someone did at some point where they managed to compile the nic drivers and include the binary blob. Because nobody gets to force you to add an empty file to your sd-card!
Yes and like me you're perfectly capable of changing a default password / using SSH keys for those critical use cases. People who use them for serious things also know how to properly handle security and in the other cases security isn't required at the level they pushing for. A simple "change password on first login" was enought.
https://www.armbian.com/download/?device_support=Standard%20support&arch=aarch64
In case you aren't aware the Banana Pi are a platinum member of Armbian and they provide money, code and general support to the project and actively tell people to use Armbian is they don't want Android. They also the the same with OpenWRT for specific models. This is true open-source collaboration, not what the Pi Foundation does, and leads to long term, well supported boards with kernel updated and paid support for enterprise customers. And why isn't the Pi Foundation also contributing to Armbian? Simple, they want to keep things for themselfs.
Making things easier for you Armbian are builds of Debian or Ubuntu with tweaks for SD cards, low level device tree overlays, kernel tweaks and everything required to have a barebones Debian system for SBCs.
The Pi is better in education, hobbyists and people who aren’t that proficient with electronics and computers however it opens the door to a lot of potencial market abuse, Apple-style ecosystems and whatnot. At the end of the day it is overpriced and it isn’t really good at anything - not even in ethics - as specialized options in those niches (ESP32, Arduino, Other SBCs, MiniPCs…) are better for said use cases. It looks a lot like the Pi Foundation knows about this market-fit issue and is just trying to push more and more stuff into the hobbits as a way to keep growing and making money. The SSH/telemetry/app bundle thing isn’t objectively bad alone, but people aren’t complaining and it is just opening the door to a LOT of more custom stuff and eventually a closer ecosystem and a situation like Chrome market dominance.
What the next step for them? A cloud service that you need to use / pay to develop stuff for the Pi? :)