Black Mirror. La miniserie

Black Mirror. Cabecera de la serie
Black Mirror. Cabecera de la serie

Black Mirror son en realidad 3 capítulos, no es ni siquiera una serie.

– El primero me ha costado verlo pero no está mal. Aunque sea ficción, hay ficción que es dificil de creer.

Black Mirror. The National Anthem. El himno nacional. Fotograma
Black Mirror. The National Anthem. El himno nacional. Fotograma

– El segundo lo he pasado por encima a las 2 minutos de lo aburrido que era.

Black Mirror. 15 Million Merits. 15 millones de méritos. Fotograma
Black Mirror. 15 Million Merits. 15 millones de méritos. Fotograma

– El tercero magistral. La interpretación de la obsesión, la investigación y el ver plasmado como invento tecnológico ese cacharro que siempre he querido tener.

Black Mirror. The Entire History of You (In Memoriam). Tu historia completa. Viendo, el interfaz de usuario.
Black Mirror. The Entire History of You (In Memoriam). Tu historia completa. Viendo, el interfaz de usuario.

Black Mirror. The Entire History of You (In Memoriam). Tu historia completa. Viendo recuerdos.
Black Mirror. The Entire History of You (In Memoriam). Tu historia completa. Viendo recuerdos.

Si sois de los que os gusta saber de qué va algo antes de visionarlo os dejo un enlace a un muy buen análisis y completo de los 3 capítulos en uno de los medios más interesantes que han surgido últimamemte, jotdown.
En jotdown la lectura plácida de artículos recupera la vida.

Actualización:
Para quien tenga curiosidad, existen casos de gente que tiene una memoria prodigiosa que se asimila al invento del tercer capítulo.
Los enlaces son estos 3:

Espero que lo disfrutéis.

How to securely activate SSH into your Synology DiskStation with SSH Keys and no root login

I like to have access to my private network at home, wherever I am, and for me the best choice is to have an ssh server available. I use it for privacy reasons, because i don’t want anyone to know what could be my email, what webs do i visit, etc. Like I explained while ago in Jump over private corporate proxy with Firefox (or git, or any SOCKS ready app) through a SSH tunnel.

As I’ve shutdown my own server to avoid the noise, power waste, gain some space, and to stop worrying about hardware or connection failures and I’ve recently purchased and advanced NAS (Synology DiskStation) I would to explain how to securely active ssh on it.

The Synology DiskStation supports both telnet and SSH, but you should never use telnet when dealing with passwords or when you don’t want to be spied, as it is completely insecure.
Everyone should instead use SSH as it is very secure and almost the standard option.

Synology DiskStation DS211
Synology DiskStation DS211

How to enable SSH and users to login

It’s easy to enable SSH on your DiskStation by going to Control Panel > Terminal & checking the box next to Enable SSH Service.
You can now log in with your root username & password. If you need to login with any other user, you need to enable user’s home and let them use login with a shell.
To enable your user’s home, go to Control Panel -> User -> User Home -> There enable the user home service.
To enable your user’s to login with a shell, you have to edit the file /etc/passwd. Here is an example with the common contents when you have 2 users, one with a enabled shell (/bin/sh) the other without:

How to enable SSH with SSH keys

But that’s not enough. Logging in with a username and password isn’t nearly as secure as requiring SSH keys. When you use password based authentication, anyone can try to reach the port and use bruteforce to gain login credentials.
With public keys authentication, you have a private key on your computer, a public key on the SSH server (the Synology DiskStation in this case). When someone tries to log in via SSH, the server looks at the public key and asks for the corresponding private key. No private key, no login.
NOTE: I’m assuming that you have already generated SSH keys. If you haven’t, you can easily find instructions on the Web.
The needed SSH daemon’s config file to allow access via keys differs from original in :
Edit /etc/ssh/sshd_config using vi, I’ve highlighted in a shortened example the changed options to harden SSH:

Save the file and restart the SSH daemon. The easier is to use the GUI/WEB login. Click on the Control Panel -> Terminal. Uncheck Enable SSH Service, apply, check it again, and press apply again.

Enabling your user public key in authorized_keys

Of course you have to copy to your home directory your ssh public key inside a ssh directory and file called authorized_keys. I would recommend to be careful with permissions.

Try logging in now, with a username enabled to login. You won’t be prompted for a password; instead, you’ll get a nice shell see:

To test our hardening Try logging in now, but use a username that doesn’t exist on the server. You won’t be prompted for a password; instead, you’ll see:

No key, no admittance. No passwords accepted. Excellent.

Extra point. No root login, just for localhost.

An allowed ssh root login for a hacker/juanker is like honey for a bear.
So what we will do is to enable ssh public key access just for our localhost..

Edit /etc/ssh/sshd_config using vi, I’ve highlighted in a shortened example the changed options to harden SSH:

And, next, include this Match rule at the end of file, as Match rules may affect all config options below it. Using without-password we allow root login using public key.

One more step is needed, repeat point “Enabling your user public key in authorized_keys” for root user.

Save the file and restart the SSH daemon. The easier is to use the GUI/WEB login. Click on the Control Panel -> Terminal. Uncheck Enable SSH Service, apply, check it again, and press apply again.

Extra point enable root login from a shell using su. DEPRECATED

DEPRECATED
Of course we still need to have root access to Synology, anything can happen.
If along any of the steps, or whatever, you have seen this error message while trying to use ‘su’:
‘su: must be suid to work properly

What is happening is that permissions on binary /bin/busybox are “wrong”, run this as root to fix it.

DEPRECATED

Restart ssh server from CLI

If you want to restart your ssh server from CLI, use this script. Running it in background guarantees that the command will be completed. Because when you launch it, your currrent ssh session will be lost/closed.

 


For some reason, this command is not fully restarting the server or not loading the modified config, so, a workaround in order to restart the ssh server is to restart the whole system.

Important

This adds a nice layer of security, but it also means that you’d better keep backups of your SSH keys, or you are hosed!
If you’ve fucked up and you can’t get a root shell or you need help because using vi is boring, try to look for a config file editor

¿Es posible reparar una hp officejet 8000 pro?

Que asco me da el mundo de las impresoras. Desde hace meses me resisto a dar por muerta a la impresora, pero ya es que ni se puede usar. No imprime, se pasa el tiempo limpiando los cartuchos, vacíandolos cual robot estúpido.
Que asco me da el mundo de las impresoras. No sólo los cartuchos son carísimos (la próxima va con cualquier recarga de tinta manual de esos que existen) además  configurarlas en linux es un dolor y para rematar ahora me es imposible encontrar en la web de HP dónde la podría llevar a reparar.
Y llevo 3 días en ello, menos mal que es una impresora casi profesional….
Al final voy a rendirme, la llevo al centro de reciclaje y compro otra.
Que asco me da el mundo de las impresoras. Me obligan al Consumismo feroz, se rompe, pues compra otra. Te quedas sin tinta, pues compra otra que es más barato que 3 cartuchos.

Bueno, si alguien sabe cómo, que deje un comentario.