That’s because they’re not going to actually do it.
Global namespace extremist. Defragment your communities!
That’s because they’re not going to actually do it.
Native? Isnt it a web app?
Gmail offers imap amd smtp access. You have to enable 2FA, and then it will allow you to create account for so called “less secure apps”.
In your place, I’d either continue using gmail directly, or finish the configuration of the self hosted mail server and just use that with any smtp/imap client. I suggest getting a separate domain for testing first, before moving your primary inbox there.
you still need good security configuration of the exposed service.
In a sense that security comes in layers, yes. But in practice, this setup will prevent 100% of bots scanning the internet for exposed services, and absolute majority of possible targeted attacks as well. It’s like using any other 3rd party VPN, except there’s not a central point for the traffic to flow through.
From the attackers point of view, nothing is listening there.
I’ve used a similar setup in the past to access a device behind a NAT (possibly multiple NATs) and a dynamic IPv4. Looking back, that ISP was a pure nightmare.
This is not a guide to hide from the government or ISP. Just a way to tunnel to your home server without publishing the sshd for random strangers. Personally, I’d just publish the ssh and be done with it.
I would rather live without the correlation attacks
The more people using Tor, the less useful targeted disconnects become.
Which is still just as open, but also a massive calling card for anyone trolling around the TOR network
Luckily, it is no longer possible to easily sniff the new v3 addresses by deploying a malicious relay. Any attack to even reveal the existence of a hidden service would require a very specialized setup. And we’re just talking discovery, not the ability to connect and attack the actual service running there.
just connecting to Tor is very much a huge exposure imho
Exposure of what, to whom?
"GhostWrite is the result of an architectural flaw, a hardware bug in the XuanTie C910 and C920 CPU. These are only two of many RISC-V CPUs, but they are widely used for a variety of applications. According to the research team, vulnerable devices include:
Scaleway Elastic Metal RV1, bare-metal C910 cloud instances
Unbacked tokens. You mean like Tether?
Exactly like Tether. USDT was never backed 1:1 by USD. They don’t even try to deny it anymore. They admit it’s backed by “various assets, including BTC”, which smells like a market manipulation.
How does Taler promote taxation?
“Customers can stay anonymous, but merchants can not hide their income through payments with GNU Taler. This helps to avoid tax evasion and money laundering.”
it might definitely be useful when used correctly in the future
I can almost see the monk smacking an orphan for holding the spoon in the wrong hand :D
GNU Taller is pretty fragile, though. One bank issues unbacked tokens and the credibility of the whole system goes down the drain. It’s the current financial system, just rebranded. Also, it promotes taxation which automatically makes it a cult & scam.
That’s interesting. I’ve initially written it off as a scam. Until I’ve learned about the proof-of-work.
Monero is great. Except for the fact that when the dev team dislikes what miners are doing, they introduce a new arbitrary rule, and everyone just goes with it. Having a process to introduce such changes unilaterally is a bug that needs to be fixed first.
Also, there’s a lightning network which allows you to transact bitcoin fast and cheap. Although the privacy aspect is still not solved there.
We also need a McDonald’s emoji, Pepsi emoji, Windows emoji and Mastercard emoji
bitcoin is not a company.
Of course security comes with layers, and if you’re not comfortable hosting services publically, use a VPN.
However, 3 simple rules go a long way:
Treat any machine or service on a local network as if they were publically accesible. That will prevent you from accidentally leaving the auth off, or leaving the weak/default passwords in place.
Install services in a way that they are easy to patch. For example, prefer phpmyadmin from debian repo instead of just copy pasting the latest official release in the www folder. If you absolutely need the latest release, try a container maintained by a reasonable adult. (No offense to the handful of kids I’ve known providing a solid code, knowledge and bugreports for the general public!)
Use unattended-upgrades, or an alternative auto update mechanism on rhel based distros, if you don’t want to become a fulltime sysadmin. The increased security is absolutely worth the very occasional breakage.
You and your hardware are your worst enemies. There are tons of giudes on what a proper backup should look like, but don’t let that discourage you. Some backup is always better than NO backup. Even if it’s just a copy of critical files on an external usb drive. You can always go crazy later, and use snapshotting abilities of your filesystem (btrfs, zfs), build a separate backupserver, move it to a different physical location… sky really is the limit here.
Distraction free? Look at all those number buttons looking like little faces. They WILL judge you, as you type. I’m pretty sure about that.
If you come from IT, you never really quit. A little parser bug here, a small race condition there, or a fucking baking oven refusing to bake until you tell it what time it is. No hope, no escape.
I’m not exactly sure what it is that I’ve just seen, but I am mildly aroused.
… is the most upvoted stackoverflow answer.