- Open Control Panel
- Navigate to Shared Folder
- Select the share with the closed lock
- Encryption menu
- Provide passphrase (if applicable)
Sunday, 8 August 2021
Friday, 23 April 2021
Passed my Microsoft Azure Fundamentals certification this week and this is my first Microsoft exam. My primary resource was Microsoft Learn where there is a lot of material broken up into 30-60 minute lessons including some labs. Also used the practice tests and did those many times before writing the cert exam itself.
Tuesday, 30 March 2021
Monday, 8 March 2021
- Learn Windows PowerShell in a Month of Lunches by Don Jones and Jeffery Hicks
- Learn PowerShell Scripting in a Month of Lunches by Don Jones and Jeffery Hicks
Sunday, 22 November 2020
Welcome to Dom617b!
At least if I've setup all the new names, redirects, and certificates. Otherwise, you're not seeing this for which I have only myself to blame. The process I think could have been simple and I'll add a few notes about where Google is tying in services.
- Go to Blogger Settings and change the name
- Disabling HTTPS first may have made things a little easier as it was initially hard to follow the redirects while that was still changing
- Change the Custom Domain to the new name
- Update DNS and with Google Domains this is at least partially integrated
- In Google Domains, verify that the "synthetic record" is registered
- OR setup DNS CNAME pointing to ghs.google.com
- Redirect old name to new and in Google Domains there is a forwarding feature
- Remove the old CNAME
- Add a forwarding entry with settings as applicable
- 301 Permanent redirect
- Redirect full path (i.e. oldsite/page.html -> newsite/page.html vs to newsite/)
- Enable HTTPS redirection
- Wait - like a day or two
- New name was resolving fine within a few minutes really
- Redirects were almost instant
- HTTPS was the slowest part
- In Blogger Settings turn on HTTPS and redirect to HTTPS if not already done
Its long past time to move on from the online handle I was using in high school so here I am Dom617b! The 617b is what I use when I can't get my own name or handle when registering for some site so that ties in to the old part, plus "617" kinda looks like "bit" in 1337 and "b" for binary, so it all comes together as a Nibble handle.
Saturday, 26 September 2020
The Synology DSM supports creating encrypted file shares and I want to use this for backups as these can contain personal files. Initial setup seems pretty flexible as you can create a share with encryption or enable encryption on an existing share and you can use key files or pass phrases and there's a feature called a Key Manager with good documentation for DSM for all of these.
My setup is to use a removable device as a key store.
It starts with setting up the Key Manager from the Control Panel under Shared Folders. From here you initialize the Key Manager and pick the USB device (otherwise internal) and set a passphrase for the Key Manager.
Then start creating shared folders that use encryption and you can pick the key manager. This also lets you pick if you want encrypted folders to be enabled automatically on boot which would require leaving your external key manager device connected.
After that, you need to keep copies of your key store and keys somewhere safe in case you lose key store device.
Once all setup you can start using that file share and it is pretty much seamless. In Windows I removed the old file history backup target and re-added the new encrypted share. On the Synology I removed the cloud backup targets, moving the files to the new location, and re-adding the cloud targets using the new location.
Stay safe 🔐
Saturday, 5 September 2020
Following actually picking and buying a NAS in Home NAS Part 1 the initial setup of the Synology is of course very easy. If you don't get distracted by all the buttons and spend days and days with "what's it do? what's this do? what's this do?"
First of all I should have gotten one of these 2 bay NAS *ages* ago and even the cheapest model would be fine. So I'll start with the list of things that are overkill in my setup.
- Dual-LAN. I just don't have enough concurrent devices to ever possibly saturate my network and since everything is WiFi even if I did, that would still be below 1 Gb that a single link would do. But it does afford a backup in case of failing cable or network port so I'm still using it.
- NVMe cache. If I can't even fill up the WiFis how could I possibly saturate the drives? I at least held back from the 2xNVMe which would add write caching as well as read caching. Current reported cache usage on the 500 GB NVMe? ~350 MB. While theoretically possible I might one day get a performance boost, does seem unlikely, don't it? It does reduce drive activity so I'll keep it in the theory that maybe the drives themselves will last longer.
- 4 TB drives. Okay so I just went with a drive size I had in budget. After copying all the data I wanted on there, usage is ~450 GB (are we seeing a pattern yet?). Truthfully, the bottom-end purchase price isn't that far off and it does forestall having to ever buy new drives except as replacements. Of all the overkill things, this is the least controversial under the heading "storage is cheap"
- Memory upgrade. Basically like the storage, I was building the spec and saw "oh, can upgrade memory, that sounds cool" and bought a DIMM for it. I think in theory I might eventually use some of that memory and the computing power in the device if I run Plex from there. Mostly I was paranoid that I wouldn't be able to get a compatible part in the future.
- The DS720+ itself comes with a 4 core CPU. I... Well it's just faster okay? We are not taking any further questions at this time.
For anyone who's had to cleanup some mail problems with Postfix configuration (or more often with other things, like anti-spam, tied in ...
In the course of troubleshooting the office Jabber server the other day, I came across some interesting info about the various caches that O...
For everyone who uses cron, you are familiar with the job schedule form: min hr day-of-month month day-of-week <command> A problem...