I'm migrating from a #LibremKey to a #Nitrokey 3c. One OTP made it to my new Nitrokey and the rest still sits on the LibremKey. I updated my OS and installed the new #nitropy utility which can't handle the LibremKey.

#NitrokeyAuthenticator is still installed on my #Librem5 and while it is easy to use that way it is even easier from my desktop. Waypipe didn't work, but ssh librem5 NitrokeyAuthenticator -platform vnc opens an unprotected vnc port…

purism@pureos:~$ netstat -pnlt | grep Nitro
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp6       0      0 :::5900                 :::*                    LISTEN      2019/NitrokeyAuthen 

…which I can connect to to get an otp before migrating it to the new token.

#NotSoSecure

And after disconnecting the ssh session the application keeps running and still can be connected to.

#EvenLessSecure

Hey #deSEC - that's such a cool service your running!

Thanks a lot - I started donating!

It works really well in conjunction with my #yunohost hosting this microblog.

https://desec.io/about

This feels strangely positive: you forget to put your #Librem5 on the charger in the evening. Next morning you get it out already with a spare battery in hand and find it running with 35% battery left.

This is such a huge improvement over the state of one year ago!

Before putting back my #yunohost #RockPro64 into my rack I measured power consumption for ~4h and ended up with ~0,158kWh/day or ~6,6W (measured between power converter and socket 230V~).

The #yunohost running this #microblogpub instance runs on a #RockPro64 in a #Pine64 nas case.

I started a year ago by installing it on an eMMC as a yunohost test, added two sata SSDs and now decided to simplify the setup by removing the eMMC boot medium.

Booting of the #SoftwareRaid configured on the SATA SSDs turned out to be less easy then I'd expected and I ended up preparing a #howto about doing this remote via ssh.

https://git.sr.ht/~chrichri/RockPro64_u-boot_SATA_software_RAID_howto

Serial connection via breakout board to my #Librem5 using a μArt serial-usb adapter.

While waiting for some press-fit headers I'm using poor mans press fit connection with nylon string.

#ShotOnLibrem5

New #Librem5 use case:

• Librem5 with a usb bluetooth dongle connected to usb-c
• the #bluetooth usb adapter is exported to my network via #usbip
• on my notebook I attach to the bluetooth adapter on the other end of our home over network
• the virtual bluetooth adapter in my notebook is connected to a windows session running in kvm
• the windows session contains software to view and configure the inverter of our photovoltaic modules

No need to sit on the floor in the room with that device to get a bluetooth connection.

Hey @telekom!

How am I supposed to destroy this written information I'm supposed to keep secret once I remembered it?

This thing survives ages...

This is really a helpful life hack I read about somewhere: for temporary connections use nylon string to hold the pins to the holes in the pcb...

Not everything perfect, yet: just used my #Librem5 to transfer money.

• connected keyboard and mouse through bluetooth (sparklan card)
• used pass-mgr-compact to get my login password for the banks page in firefox
  • found passff not working in my actual firefox configuration
  • had to copy the username from pass in a terminal, because I didn't find a way to get it in pass-mgr-compact
• read the email containing information about the transfer in geary
• confirmed the transfer using an external token that reads data from the screen of the L5

On the first try the L5 froze when I connected power after disconnecting the #LibremKey needed for my pass tomb from the L5.

Wrote this in #tangram.