Press "Enter" to skip to content

Category: Life: Work and Techy

Windows 10 OpenSSH – Storing keys using the SSH agent

This article is the second of a series I’ve written about migrating from using PuTTy on Windows to using the native OpenSSH client now available on Windows 10: you can read the rest of the articles via: Installation Storing keys using the SSH Agent < You are here Importing existing keys Creating a new public/private key pair Other useful OpenSSH commands Configuring Windows Git To manage the OpenSSH keys, you need to add them to the ssh-agent (think of it as PuTTY’s Paegant). These keys will then be added to the user’s “Windows registry” and encrypted to their user profile (so, even if the key has an individual password on it, if somebody logins into your machine as user and has access to the registry, then they can access your private keys – if they log in as somebody else, your keys should be safe). This sounds like a security weakness, but is how MacOS and Linux handles keys anyway! Continuing in the Administration Powershell, we’re now going to start the SSH-agent which makes key management much easier: Start-Service ssh-agent If you get an error such as Start-Service : Service ‘OpenSSH Authentication Agent (ssh-agent)’ cannot be started due to the…

Smart Meters (1/2): Why you shouldn’t get one

Quite a few electricity and gas companies in the UK are ‘encouraging’ customers to get smart meters installed, but here are a few reasons why perhaps you should turn down these optional meters. I don’t necessarily agree or disagree with any/all of these points (in fact, I’ve also done a list of reasons why you should perhaps get one), but these are just ones I’ve heard/come across: SMETS1 restrictions. The ‘current/previous’ generation of smart meters, SMETS1, tend to be ‘locked’ to the installing company/supplier and become ‘dumb’ (unable to report readings/in home display inaccurate etc) if you move to another provider. The ‘new-gen’ SMETS2 meters (which will be rolling out this year – 2019) are multi-provider compatible. Privacy. Some people don’t like the idea of energy companies/Capita (who provide the ‘backend’ – DCC – to SMETS2 meters) knowing practically down to the minute how much power you are consuming (good indication of when you get up, when the house is empty, when you are cooking dinner etc etc) Security. Smart meters are electronic devices and therefore can be hacked (it’s currently unknown how easily/feasible though: yes, they use encryption but they have been plenty of insecure encryption deployments in smart…

Smart Meters (2/2): Why you should get one

As a counter-argument to my previous post as to why you shouldn’t get a smart meter for your electricity and gas, here’s a list of reasons why you perhaps should. I would suggest though waiting for your supplier (I use Bulb Energy and do recommend them – plus if you switch with my affiliate link we both get £50 credit and cheap gas and electricity) to roll out ‘SMETS2’ smart meters as these will continue working ‘in a smart manner’ no matter which supplier you are with whereas ‘SMETS1’ (the ‘current/previous’ generation) ones usually stop reporting meter readings when you switch suppliers or their in-home displays become inaccurate/stop working. Reducing running costs. Suppliers no longer need to send out meter readers to get accurate readings (especially from people who can’t/won’t provide readings themselves). This means they can keep their prices low and give you lower bills More accurate bills. Provided your meter reading a day or two early or unable to read your meter one month? Then you were probably getting an estimated bill – now with the data flowing to the supplier, you needn’t worry as they supplier can get the meter reading just when it is needed for…

NodeJS : UnhandledPromiseRejection handling

Are you programming Node JS Javascript and reached the dreaded: (node:1984) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): xxxxx (node:1984) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. but can’t figure out where the Promise is in NodeJS which is causing this? Just add the following bit of code near the top of your code (after the requires if used) which might help: process.on(‘unhandledRejection’, function(reason,promise) { console.log(‘unhandledRejection’, reason); });