I tried but got an error:
:& : Command not found
Is it expected ? Did I type something wrong ? I'm confused...
I tried but got an error:
:& : Command not found
Is it expected ? Did I type something wrong ? I'm confused...
Tabs for indent, spaces for alignment. This is the way, I can't believe people are still fighting that ?
Because other people might have restricted environment which might not suit their preference is not a good reason to level it down IMO.
Also, I think 9 is the best size for indent (matter of preference), do you think I should switch to space so everyone can enjoy this wonderful view I have ?
Weight your words my friend! GNU's a behemoth !
GCC alone is almost as big as Linux. Add core/binutils, the Hurd, ... And you easily outclass the kernel itself !
~ $ du -sh linux-6.4.12/ gcc-13.2.0/ 1.5G linux-6.4.12/ 1.1G gcc-13.2.0/
Oh, and Emacs.
IPv4 and IPv6 are two different network stacks. Your IPv4 stack is hidden behind wireguard, but not the IPv6 one.
The correct way to fix your issue is to setup a second witeguard tunnel for IPv6, and route IPv6 traffic through it.
Edit: many comments advise to block outbound IPv6 traffic. Don't do that! It will add latency to all your requests as you will have to wait for them to timeout.
I'm reading all the comments and I'm shocked... In France, with uncapped access and 1Gbps down/600Mbps up (theorical) I pay 40€/mo (30€ every six month when I call to complain that it's too expensive). And it's definitely not the cheapest provider.
That's insane !
I get what you say, and you're definitely not wrong to do it. But as I see it, you only saved ~80Kib of ingress and a few lines of logs in the end. From my monitoring I get ~5000 failed auth per day, which account for less than 1Mbps average bandwidth for the day.
It's not like it's consuming my 1Gbps bandwidth or threatening me as I enforce ssh key login. I like to keep things simple, and ssh on port 22 over internet makes it easy to access my boxes from anywhere.
Congratulations! A mail server is quite demanding in terms of initial setup, but it's also very rewarding !
Here are a few pointers I can give you:
ip4:
and/or ip6:
selectors for SPFThis should limit a lot your likeliness to end up in spam folders (which is usually the hardest part about running your mail server)
You don't need to access a .onion instance to use Tor. You can simply perform your day-to-day web usage through Tor directly.
On your phone, you can even use Tor natively with most of your apps.
ELI5
So it's saturday afternoon, a very hot one, so you ask your daddy for an ice cream (hosted service). The shop you go in is very bizarre though, as there is one vendor (TCP port) for each flavor (docker service/virtualhost). But it's tricky because they're all roaming in the shop, and you don't know who's responsible for each flavor. Your dad is also not very comfortable paying these vendors directly because they only accept cash and do not provide any receipt (self-signed certificate/no TLS).
Hopefully, there is the manager (reverseproxy) ! This girl is right where you expect her: behind the counter (port 80/443), accept credit cards and has a receipt machine (Domain name + associated certificate). She also knows everyone on her team, and who's responsible for each flavor !
So you and your dad come to see the nice lady, ask for a strawberry + chocolate ice cream, and pay her directly. Once done, she forwards your request directly to the vendors responsible for each flavor, and give you back your ice cream + receipt. Life is good, and tasty !
Don't even bother with a SWAP partition. Create an empty file on your / partition so you can grow/shrink it as needed.
did if=/dev/zero of=/SWAP bs=1024m count=4
mkswap /SWAP
swapon /SWAP
endlessh was pretty cool and a more modern version is even better ! I'll give it a shot !
On a side note, I found a way to trap HTTP connections too while working on my cyb.farm project. The go implementation is ridiculously simple: tarpit.go. It works by providing an endless stream of custom headers to the client, which it is supposed to ingest before getting to the content itself.