Those were the days...
94 posts • joined 25 May 2011
My iPad chargers have a completely standard USB output, it's only the cable that has a Lightning connector on one end. So what's the fuss about chargers?
IMNSHO, standardizing wall plugs would make a lot more sense.
(Paris, because I'm sure she doesn't understand either --->)
They do have one significant advantage: The WAF (Wife Acceptance Factor). It's the only kind of pc-style box permitted in the living room to power my media center (MythTV on Linux) - anything else was vetoed as too big/klunky/noisy/ugly.
For bonus points I replaced the minitower PC in the office at home with a second NUC. A bit pricey - sure, but much cheaper than an iMac.
How many of us IT pro's do something similar - keep tons of files in odd places?
Personally, I tend to hoard all sorts of stuff in my Downloads folder - so much so that I have subdirectories there. Bloody annoying when working from home without my company laptop because this folder is not synchronized to OneDrive.
I know of several people who store passwords in their contact lists. Anything from Facebook and Gmail to the PIN-code for their rately used credit card.
Yep it is a stupid idea and they should use a proper password manager, but changing habits from what you did back in the Nokia days is hard.
I'm with you on that one - it is one of my favourite features of Notepad++ that you can open a new file, and it will automagically be saved somewhere in the bowels of the programs filespace until you do give it a proper filename yourself.
Now, where was that configuration file template - "New file 283" or 316 ...
--> Paris 'cause she never thinks about saving, only spending.
Usenet existed more than 30 years ago. Tiny pictures were posted on alt.sex.pictures in uuencoded form split into multiple posts because the size of posts was limited to a few kB (yes, KILO bytes, not MB), so you had to download each post, strip off the headers and run it through uudecode before viewing a tiny 200x140 pixel image on your 640x480 16-color CGA screen.
Nowadays 12-year olds post selfie-porn on social media.
No way. The Royal Mail equivalent around here (Denmark) takes minimum 5 days to deliver any letter or package. I suppose they need to ship them via GCHQ to make sure the t-shirts I ordered haven't been infested with some evil RFID chip...
They're clever enough not to have the rerouting show up on the tracking page, though.
(Yes I will go take my anti-paranoia pill now, don't worry).
There was a time when I worked for CSC as admin on some systems which a large insurance company had outsourced. My experience was in web middleware (Weblogic, Websphere and that sort of stuff), but this particular installation had a mission-critical installation using Oracle Forms. Which is tightly tied into an Oracle database.
Well, I was deploying a deployment of an update to the Forms application on a Friday evening, and was running short on disk space. So I took a look around and found a directory with a bunch of <whatever>.LOG files taking up a lot of space. Since logs were being collected on a central server, I assumed these had to be something which could be wiped and promptly did a "rm -f *.LOG".
Little did I know that an Oracle database keeps all pending transactions in a transaction logfile, aptly named <whatever>.LOG ...
So after moving the new forms files into place I tried starting the database and got a completely unknown error, but enough for me to recognize that those logfiles probably were a bit more critical than I had assumed.
My good luck was that the database had been shut down when I deleted the logs, so after a frantic bit of google'ing and some Oracle commandline magic the database finally did start without any loss of data.
I have to admit I kept this to myself, but from then on I insisted that there was a database admin on call for future deployments.
As seen from this (eastern) side of the pond, it is not only the US politicians who are clueless. The general population know even less about how surveillance capitalism work, and will happily divulge any and all personal details if only there's a chance of winning a free doughnut.
It really is the same thing in Europe, we are just lucky that our politicians - miraculously, I have no idea how it came to be! - implemented reasonable privacy measures with the GDPR.
Because certificates typically expire after 2-3 years - beancounters and bosses cannot see that far ahead (except when pulling "strategies" out of various orifices).
Even the IT monkeys doing the renewals have moved to new offices at least 3 times, so that two your old calendar with the post-it notes? Noone remembers what it was for, so it goes down the bin.
'Users will be relieved to know that the team is indeed actually looking at feedback, even if it seems to be skipping the “stop the thing deleting my stuff” entries in favour of “make search a bit faster.”'
You don't seem to understand that these two work together. With all user files deleted, there is a lot less to index. Hence search runs faster.
As others have mentioned, sudo gives you much more fine-grained control over who is allowed to do what. But there are other advantages over plain su:
- You have an audit trail of who ran which admin command when. For some of us, that is a compliance requirement.
- Communicating a shared password is difficult. Tends to happen via e-mail which is NOT secure.
- When you have 20+ servers, changing the administrator password because Joe Admin left the company is not so simple.
- Passwords can be cracked or leaked, so a security compromise of one server quickly becomes a site-wide problem (unless you use unique passwords, which complicates the distribution issue further).
I try to avoid passwords as much as possible, to the extent that my personal servers do not have passwords (a '!' for the password field in /etc/shadow). Logins can only happen via ssh using SSH keys or certificates, and sudo is setup to require a one-time password or physical token (Yubikey). If you must use passwords, at least make sure you keep them centralized (ldap directory or similar).
In other words, think about how you implement security instead of just bashing some random tool based on a 7 year old forum post.
As you said, OpenVPN does what it claims to do - nothing wrong with that. But Wireguard does have some things going for it:
1) It doesn't rely on OpenSSL for encryption, so there is a whole lot less code to audit if you want to check for security problems
2) It is a kernel module implementation (at least on Linux), so the processing overhead is much smaller and it should be able to scale to wirespeed while handling multiple connections. It also means that it works like any other network interface, so the usual configuration files and network scripts will take care of running your VPN.
3) Authentication and setup is much simpler, since it is a trust-on-first-use so no need for setting up your own CA.
Have a look at it, it does work quite well.
Had a database server bickering about being short of disk space. Without knowing much of Oracle internals, I found some very large *.log files lying around and promptly deleted them - I mean, there's no need to keep those old system logs, right?
So I learned the hard way what database transaction logs are. And how to convince Oracle to create a new set of transaction log files when starting up.
Fortunately, it was a very quiet database.
Since it was in the Windows for Workgroups days, TCP/IP was most likely not used. Just some random address assigned by the NIC and running Netbios, IPX or some other abominable protocol.
Personally, I would have made the PC speaker start screaming at the user with a NSFW vocabulary. Guaranteed results much quicker.
7. The fridge, being an intelligent IoT device, will notice that it needs to stock up on fresh milk, but since there is no Wifi connection in the asteroid belt it will fail to connect to Walmart and subsequently the control system crashes with an unexpected error. The thrusters therefore fail to fire, and the fridge crashes back to Earth.
is about as quaint as remembering phone numbers.
Face it - one of the goals of ANY new IP version is to extend the address range. So no matter how you design the protocol, you end up with more numbers per address. Saying that it is easier to remember 184.108.40.206 than 2a00:1450:400f:802::200e just does not make sense. What you CAN remember is "google.com".
Which is why we invented DNS.
Biting the hand that feeds IT © 1998–2020