How to Talk to Your Family About Digital Security



  • You and your family are sipping hot cocoa, gathered around the [holiday object of your choice], and your family member suddenly asks: “Can you help me with my [insert device here]?”

    They need a question answered about their computer, phone, tablet, video game console, or internet-connected device. Maybe they have related questions about their online accounts.

    Or maybe there is a teenager or college student in your family that posts intensely personal information online, and has just realized that they should probably maintain more privacy in their online lives—but isn’t sure how to start.

    Or perhaps the conversation of data breaches comes up around the dinner table, and Uncle Navid insists that the only way to protect yourself is to never go online at all.

    Congratulations, you are now responsible for threat modeling for the holidays!

    This is a good time to take a step back, consider some common concerns and threat models, and talk to your family about digital security. Congratulations, you are now responsible for threat modeling for the holidays!

    Before you begin, try to take a harm reduction approach to answering their problems. Take a moment to think about what devices and operating systems they use, what workflows they already have in place, and what kind of advice might they be receptive to.

    Then, you can start to narrow down on their concerns. A good way to start is by asking: “What would you like to do, and what are you worried about?”

    Threat Modeling for the Holidays

    As you are teaching your friends and family, you might encounter one of the following attitudes:

    “I have nothing to hide, so why do I need to protect privacy?”

    “I am worried about my digital security to the point of being overwhelmed. I don’t know where to start.”

    “I’m ready to take action, but not until I have a perfect handle on how all of these technical concepts fit together.”

    “There’s no such thing as perfect security, so why even bother? If someone wants to hack me, they’ll figure out a way to do it.”

    If you’re struggling with keeping them motivated to learn, try out some of these ideas.

    Help your friends and family move into the new year with added security. Let us know how these lessons go by submitting feedback to the Security Education Companion, and by using the hashtags #TheSafestConversationYoullHaveThisHoliday or #BadgerYourFamily.


Log in to reply
 



Tmux Commands

screen and tmux

A comparison of the features (or more-so just a table of notes for accessing some of those features) for GNU screen and BSD-licensed tmux.

The formatting here is simple enough to understand (I would hope). ^ means ctrl+, so ^x is ctrl+x. M- means meta (generally left-alt or escape)+, so M-x is left-alt+x

It should be noted that this is no where near a full feature-set of either group. This - being a cheat-sheet - is just to point out the most very basic features to get you on the road.

Trust the developers and manpage writers more than me. This document is originally from 2009 when tmux was still new - since then both of these programs have had many updates and features added (not all of which have been dutifully noted here).

Action tmux screen
start a new session tmux OR
tmux new OR
tmux new-session
screen
re-attach a detached session tmux attach OR
tmux attach-session
screen-r
re-attach an attached session (detaching it from elsewhere) tmux attach -d OR
tmux attach-session -d
screen -dr
re-attach an attached session (keeping it attached elsewhere) tmux attach OR
tmux attach-session
screen -x
detach from currently attached session ^b d OR
^b :detach
^a ^d OR
^a :detach
rename-window to newname ^b , <newname> OR
^b :rename-window <newn>
^a A <newname>
list windows ^b w ^a w
list windows in chooseable menu ^a "
go to window # ^b # ^a #
go to last-active window ^b l ^a ^a
go to next window ^b n ^a n
go to previous window ^b p ^a p
see keybindings ^b ? ^a ?
list sessions ^b s OR
tmux ls OR
tmux list-sessions
screen -ls
toggle visual bell ^a ^g
create another window ^b c ^a c
exit current shell/window ^d ^d
split window/pane horizontally ^b " ^a S
split window/pane vertically ^b % ^a |
switch to other pane ^b o ^a <tab>
kill the current pane ^b x OR (logout/^D)
collapse the current pane/split (but leave processes running) ^a X
cycle location of panes ^b ^o
swap current pane with previous ^b {
swap current pane with next ^b }
show time ^b t
show numeric values of panes ^b q
toggle zoom-state of current pane (maximize/return current pane) ^b z
break the current pane out of its window (to form new window) ^b !
re-arrange current panels within same window (different layouts) ^b [space]
Kill the current window (and all panes within) ^b killw [target-window]
  • FYI for FreeBSD the driver only supports block size chunks, therefore:

    dd if=/dev/cd0 of=/name-the.iso bs=2048

    read more
});