• 2 Posts
  • 115 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle




  • Last time they tried our grandparents took 105 days to beat Russia with very little formal military and even less hardware. Sure, we had some help back then too, but today it’s on a whole different level. And we’re just a single small country up north, NATO as a whole is quite a bit bigger.

    Russia currently has lost million soldiers and stockpiles of soviet relics are pretty much empty with a strong breeze away from total economy collapse. They don’t have power to conquer a potato field from a modern western country right now, much less against the whole global west.



  • I actually did something for quite a while. Finished long overdue wiring for outdoor access point and one more camera, replaced a main switch since the old one started to behave unreliably, installed frigate (which still needs some work), cleaned up some wiring while messing around, updated a bunch of firmwares, replaced switch in garage to managed one and made some changes on my workstation and some other minor stuff.

    Next would be to move cameras into their own VLAN and harden that setup a bit. And I really should get around on better backups for my VPS. But it’s a new week coming up, if the work isn’t too busy I might get something more done.




  • DNS PTR records belong to the entity who owns the IP addresses, you can’t make reverse records for arbitary addresses like you can with forward zones. I haven’t heard about any residential ISP which would give access to PTR records and even on business lines that’s usually a premium.

    What you could do is to get a VPN service which gives you these options, if there is one, I don’t know. Most likely you’re looking for a VPS for that and tunnel traffic with some kind of VPN-setup to your local instance. And at that point you might as well run the whole thing on VPS unless you happen to need a ton of storage or some other reason makes pure VPS server too expensive.





  • Since no one has yet mentioned, by default if you’re running tar as a non-root user it extracts files with owner/umask of the current user and if you run it as root (or superuser) it’ll preserve ownership and permissions. From tar man page:

    –no-same-owner

    Extract files as yourself (default for ordinary users).

    –no-same-permissions

    Apply the user’s umask when extracting permissions from the archive (default for ordinary users).

    As mentioned, with root the defaults are to keep UID/permissions as they are in the archive. (–preserve-permissions and --same-owner).



  • It’s quite likely that any given IP, unless you get one from shady VPS provider or something, is “clean”. And if it’s not it’s usually not that big of a deal to get it cleared from major blacklists (spamhaus, google and microsoft covers quite a lot). You just need to dig up proper forms to tell them that you’re a new owner of said IP and promise to play nice.

    Same goes with domain names, but if you get a new one that’s a non-issue. Just set up SPF-records properly (and preferably DKIM/DMARC, but those aren’t strictly necessary and need a bit more than a single TXT-record) and you’re good to go.

    And then you of course need to stay away from those lists. If you configure your SMTP to act as a open proxy you’ll be on every shitlist on the planet pretty quickly. So, reasonable measures against compromised account (passwords, firewalls, rate limits…) and against other threats (misconfigured/unsafe web service used for spam and stuff like that). Any of those alone are not too difficult to accomplish, but there’s quite a few things you need to get right.


  • Maybe easier to get anything runnin quickly. But it obfuscates a lot of things and creates additional layer of stuff which you need to then manage. Like few days ago there was discussion about how docker, by default, creates rules which bypass the “normal” INPUT rules on many (most?) implementations. And backup scenario is different, it’s not as straightforward to change configuration than with traditional daemon and it’s even more likely to accidentally delete your data as a whole.

    As I already said, docker has its uses, but when you’re messing around and learning a new system you first need to learn how to manage the ropes with docker and only after that you can mess around with the actual thing you’re interested of. And also what I personally don’t really like is the mindset that you can just throw something on a docker and leave it running without any concern which is often promoted with ‘quickstart’-type documentation.


  • You absolutely can run services without containers and when learning and trying things out I’d say it’s even preferable. Docker is a whole another beast to manage and has a learning curve of it’s own.

    Containers can of course be useful but setting everything up, configuring networking, managing possible integrations with other components (for example authentication via LDAP) it’s often simpler just to run the thing “in traditional way”. With radicale you can just ‘apt install radicale’ (or whatever you’re using) and have a go with it without extra layer of stuff you need to learn before getting something out of the thing. And even on production setups it might be preferred approach to go with ‘bare metal’, but that depends on quite a few variables.


  • IsoKiero@sopuli.xyztoSelfhosted@lemmy.worldWhat I host myself
    link
    fedilink
    English
    arrow-up
    18
    ·
    2 months ago

    On residential connections it’s a bit pain in the rear, but if you get VPS (or something similar) it’s perfectly manageable. You just need to maintain stuff properly, like having proper DNS records, and occasionally clear false positives from spam lists. The bigger issue is to have proper backups and precautions, I’ve hosted my own emails for over 10 years and should I lose all the data and ability to receive new messages it would be a massive personal problem.


  • it’s really hard to prove that a candidate was rejected because of their ethnicity

    Same in Finland at least to some extent. Statistics and published tests show that you’re less likely to get even an interview if you have a foregin sounding name but of course the official reason is always something ‘acceptable’. And when hiring people the reason can be whatever, “not good fit for our team”, “other applicants had better suited skill set”, “not enough experience in X” and so on. All perfectly good reasons to pick someone else in theory and in practise it’s impossible to prove any racism on selection.

    Obviously not everyone does this and any of those can be a real reason to pick someone else even without any racism (intended or not), but it’s still common enough to be statistically meaningful.