187
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Apr 2024
187 points (94.3% liked)
Selfhosted
62183 readers
306 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
founded 3 years ago
MODERATORS
If I were you I might try deploying a mini enterprise network with permissions and things. It would be fun to do it with active directory to try to practice pentesting, or it would also be fun to do with linux to try to learn more about deploying linux in enterprise environments.
This is pretty high on the to-do list. I plan on virtualization a bunch of it, but it would be pretty easy to have one desktop hosting each subnet of client PCs and one hosting the datacenter subnet. Having several hosts to physically network means less time spent verifying the virtual networks work as intended.
Also playing with different deployment tools is a goal too. Having 2-3 nearly-identical systems should be really useful for creating unified Windows images for deployment testing
I don't like windows, so I don't deploy any of this for real, but yesterday and the day before I set up a windows server, a few clients, and a Kali VM and manager to get in. I found out if you type "\\anything" into the windows bar it will send that user's name and hash out very easily with llmnr poisoning on every keystroke. What's worse is that is the default behavior. It is super fun to learn about all this though.
Edit: upon posting this comment it made the double backslash look like a single backslash so I changed it to a triple so it looks right on my end but just know I meant for it to be double.