EFF Supports the Adoption of Berkeley's Surveillance Technology Use and Community Safety Ordinance



  • Across the nation, much of the American public remains unaware of the risks to privacy and freedom of expression posed by steadily advancing surveillance technologies. Automated license plate readers, cell-site simulators, and facial recognition equipment—once confined to the imagination of science fiction authors—have all become common tools for police surveillance. Spy tech is often marketed to local law enforcement agencies with claims (often unsubstantiated) of enabling crime reduction without the need to expand police department personnel. However, the adoption of this equipment and failure to establish critical policies regarding its use presents substantial risks to privacy, as well as civil rights.

    Since 2016, we’ve worked with a range of local and national partners on empowering communities to take control of surveillance equipment policy and acquisition. These coalitions have supported cities across the United States in proposing ordinances that would provide consistent transparency, accountability and oversight measures.

    Two such proposals are currently under review in the San Francisco Bay Area.

    Oakland’s Privacy Advisory Commission recently finalized its recommendation to the Public Safety Committee regarding Oakland’s proposed Surveillance and Community Safety Ordinance. The Privacy Advisory Commission was created as the result of Oakland residents’ rejection of the proposed expansion of the Domain Awareness Center into a citywide surveillance network. In addition to work in their own community, Oakland Privacy, whose efforts were fundamental in the creation of Oakland’s Privacy Advisory Commission, has been a leading ally in our work to support the adoption of similar bills, not only in Oakland but throughout the Bay Area.

    The City of Berkeley, a neighboring community that has been the recipient of this support, is scheduled to hold a hearing on its own Surveillance Technology Use and Community Safety bill on Tuesday, December 5. With our coalition partners we submitted a letter in support of Berkeley’s ordinance on November 20, asking the Berkeley City Council to recognize that, now more than ever, local leaders have a special responsibility to enact strong measures that protect vulnerable residents from suspicionless monitoring and the creation of databases exploitable for discriminatory ends.

    As we write in the letter:

    The Ordinance is straightforward: it requires essential transparency, accountability, and oversight for all surveillance technology proposals, and it ensures the public has the opportunity to learn about the civil rights and civil liberties impact of surveillance technologies before local officials acquire them.

    EFF also has supported laws to ensure community control of police surveillance for Santa Clara County, BART, Palo Alto, and statewide.

    The power to decide whether these tools are acquired, and how they are utilized, should not stand unilaterally with agency executives. Instead, elected City Council members should be empowered with the authority to consider and responsibly approve, or reject, surveillance technology. Most importantly, all residents must be provided an opportunity to comment on proposed surveillance technologies, and the policies constraining their use, before representatives decide whether to adopt them.





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]
  • Use the same script for updating/ upgrading

    Make sure to change the versions to the latest releases:

    #!/bin/bash set -e bpcver=4.2.1 bpcxsver=0.57 rsyncbpcver=3.0.9.12

    Scroll through the script, know what you are doing.

    Uncomment the upgrade section(s) and comment out the install section(s)

    read more
  • Again running smartctl after all is said and done:

    smartctl --all /dev/sda

    ddrescue-smartctl-after-rescue.png ddrescue-smartctl-2.png

    Yet an old drive in itself, I run the wheels off of them, and monitor regularly as anyone should.

    read more
});