close
  • person chevron_right

    "Linux users do have some choices when it comes to distributions that help protect their privacy and security."

    Anonymiss – Tuesday, 31 January, 2017 - 02:33

  • chevron_right

    Trying out Mosh – the Mobile Shell

    Matija Šuklje – Saturday, 7 January, 2017 - 09:01

While browsing around wikis while waiting for the new kernel to compile on my poor little old ARMv5 server, I stumbled upon Mosh.

On its home page we can find the following description:

Remote terminal application that allows roaming, supports intermittent connectivity, and provides intelligent local echo and line editing of user keystrokes.

Mosh is a replacement for SSH. It's more robust and responsive, especially over Wi-Fi, cellular, and long-distance links.

… but what it boils down to is that if you even just occasionally have to SSH over an unstable WLAN or mobile internet, you should instead use Mosh.

The syntax seems very similar to OpenSSH and in fact, it does run on top of it (at least for authentication, then it uses its own AES-encrypted SSP over UDP). But the way it works, makes sure that even if you lose connection for a while, it will resume just fine. It also gets rid of network lag when typing and is in general very responsive.

Mosh is great for logging into remote shells, but you will still need to use OpenSSH for scp and sftp, as Mosh is optimised for character (and not binary) transport. Which is perfectly fine.

This is one of those tools that when you first try it out you simply go “Dear $deity, finally! Why Whhhhyyyyy haven’t I used this before …so many needlessly lost hours with SSH timing out …oh, so many.”

hook out → coming soon: Armbian on Olimex Lime 2 to replace (most) of my current Gentoo on DreamPlug

  • chevron_right

    Slack Privacy Policy

    Timothée Jaussoin – Wednesday, 6 January, 2016 - 07:37 edit

For every teams that are using Slack. Be sure that you are ok with the Privacy Policy of the platform.

We may employ third party companies or individuals to process personal information on our behalf based on our instructions and in compliance with this Privacy Policy. For example, we may share data with a security consultant to help us get better at preventing unauthorized access or with an email vendor to send messages on our behalf. We may also share data with hosting providers, payment processors, marketing vendors, and other consultants who work on our behalf.

We may also share aggregated or de-identified information with our partners or others for business or research purposes. For example, we may tell a prospective Slack customer the average number of messages sent within a Slack team in a day or may partner with research firm or academics to explore interesting questions about workplace communications. Again, this policy is not intended to prohibit the disclosure and use of aggregated or de-identified data.

All the communication made with Slack are saved on their servers in a way that they can have access to everything in a quite simple way (including conversation history, files…).

And to clarify the last sentence in bold, if I understand correctly (correct me if I'm wrong) : "this policy allow the disclosure and use of aggregated or identified data (with our partners)".