I use ssh regularly, I just use a different key for each server. And thus I don’t use the default name (id_rsa) because it doesn’t make sense.
I use ssh regularly, I just use a different key for each server. And thus I don’t use the default name (id_rsa) because it doesn’t make sense.
Here you go!
~ $ cat ~/.ssh/id_rsa
cat: /data/data/com.termux/files/home/.ssh/id_rsa: No such file or directory
~ $ cat ~/.ssh/id_ed25519
cat: /data/data/com.termux/files/home/.ssh/id_ed25519: No such file or directory
For all the mentioned cases, if your firewall blocks incoming packets by default, no one can access it, no matter what is the source of the port being open.
You don’t configure it on the docker level, at least if you care about outside connections. If you mean from your local computer to a docker container, by default you cannot connect, unless you expose the port to the system. If you mean from other docker containers, just create your own separate network to run the container in and even docker containers cannot access the ports.
I usually use netstat -tulpn
, it lists all ports, not only docker, but docker is included. docker ps
should also show all exposed ports and their mappings.
In general, all docker containers run on some internal docker network. Either the default or a custom one. The network’s ports don’t interfere with your own, that’s why you can have 20 nginx servers running in a docker container on the same port. When you bind a port in docker, you basically create a bridge from the docker network to your PC’s local network. So now anything that can connect to your PC can also connect to the service. And if you allow connection to the port from outside the network, it will work as well. Note that port forwarding on your router must be set up.
So in conclusion, to actually make a service running in docker visible to the public internet, you need to do quite a few steps!
On Linux, local firewall is usually disabled by default, but the other two steps require you to actively change the default config. And you mention that all incoming traffic is dropped using UFW, so all three parts should be covered.
I’m using Proton mail, I like their focus on privacy and e2e (only with other Proton users, though).
All five of them.
Doesn’t it break a lot of things? Half the stuff refuses to work when some specific files have too permissive chmod.
I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they’re rich and can afford it.
Well, Fedora 40 here as well and it just doesn’t work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though.
Like trying to destroy people’s lives so they can make a few dollars.
Nah, php over python any day. Equally easy to start, equally fucked up core, but the ecosystem around it is so much saner and easier. And I’d argue it’s even easier for beginners.
Unless you need something that only has python bindings, I’d never choose python.
Stop projecting, maybe? No, I’m not forced. But I want to, because I refuse to pay any more money to such a shitty company. I paid for the product, now I’m gonna use it the way I want to.
Price is not my reason for pirating. Seriously, people are different from you, stop assuming that everyone has the same motivation as you do.
I mean, who doesn’t? But nah, I just don’t want to pay a company that does as much horrible stuff as Nintendo does. That pretty much means I own an expensive paperweight which I’m not a huge fan of as well. So I decided it’s gonna be a pirating only console.
I don’t like the way Nintendo destroys people’s lives just because they “lost” a few dollars.
So it will become a MIG switch only system, right? Also, how does one get caught? I’m not into online games in general, so I wouldn’t be playing any multiplayer games. Is the simple fact that the game’s certificate was used on multiple devices simultaneously enough to flag the device?
We use .lh, short for localhost. For local network services I use service discovery and .local. And for internal stuff we just use a subdomain of our domain.
There are several bad architectural decisions and when your architecture is wrong, the quality of the code itself doesn’t really matter (to be more specific, I was talking about architecture in my previous comment, not the code itself, I don’t know Rust so I can’t really comment on that).
To fix the architecture, major parts would have to be rewritten, almost making it a different codebase, because pretty much no part would be left unturned.
The codebase is extremely shitty, instead people opted for complete rewrite.
I personally only turn it off when someone’s visiting over night and the noise disturbs them, otherwise I just leave it on nonstop. Mainly because it would annoy me to try to open whatever and find out I have to turn on the server first. I don’t have a UPS and never even thought about getting one (for the server, I’m thinking of getting one for my 3D printer).
It’s sad that this is considered malicious at all. Seriously, either working from home is a risk for your company or it isn’t, there’s nothing in between.
cat ~/.ssh/*
perhaps?