A.K.A.
@AlexanderESmith
@AlexanderESmith
There’s no need to encrypt this data. Any entity that is watching you knows how to see the domains you visit, and everything on this site is on the main page, or a click away from it.
An SSL here is nothing more than security theater, or marketing.
I might have missed it, but it doesn’t look like their site accepts payment data, or has a login of any kind.
Why would the lack of SSL concern you?
Agreed on all counts.
My reply initially had a “if you had a fleet of these things…” addendum, but OP’s post read (to me) as though he was converting commodity hardware into a makeshift home server, so I removed it because it was almost certainly not relevant.
You’ll waste more time trying to figure out how to do this than it would take to move a monitor and keyboard to the server, do the install, and plug the monitor and keyboard back into your main computer. Once the server is up, you can administer it over the network via ssh.
The number of hours I put into figuring out what X was, the difference between XFree86 and X.ORG , fixing resolution and DPI issues, installing video card drivers (mostly nVidia)… I think all that tinkering prepared me for my career as a systems admin.
I think Slackware came with KDE, which is probably why I leaned toward it for so long. I’ve been using XFCE for many years, now.
rsync can resume partial transfers, but you really should break that file up. Trying to do it in one go is crazy.
Oh I remember those disks :D I think I had to either pull them off the ISO, or download them separately so that I could boot the system to the point where A: the install could occur at all and B: it had enough drivers to use the CD-ROM drive XD
My first distribution was Slackware 7.1 when I was in high school. It took a week to download the .iso on dialup, and I had to use a download manager (GetRight) so that I could resume the partial download any time the connection dropped (usually because someone had to use the phone).
I’m old o_o
I still vividly remember not being able to figure out how to install new packages, or knowing how to compile from source.
You left out that they refuse to let end users control updates on the system unless they resort to hacky bullshit (and even that doesn’t work consistently). As far as I know (and have experienced on Windows Server) this extends to enterprise as well.
“Best practice” isn’t a catch-all rebuttal. Best practices are contextual. I’m keen to see your justification for encryption beyond “all sites should encrypt everything always”.
My assertion is that this isn’t necessary in this case. Why do you think that it is necessary to encrypt open-source, freely available, non-controversial site content?