Senator Calls on Courts to Increase Transparency of Surveillance Orders



  • Federal courts must end the excessive secrecy surrounding law enforcement surveillance orders, a U.S. Senator urged in a letter on Friday. This secrecy block’s the public’s ability to fully understand how police conduct this surveillance, the lawmaker wrote.

    The letter, sent by Sen. Ron Wyden (D-Or), asks federal courts to enact several important reforms, including establishing uniform procedures for publicizing basic information about when and how often law enforcement seeks information about our communications and other data held by services such as cell phone companies, Internet service providers, and online platforms.

    The information law enforcement can obtain with these orders can often provide considerable insight into people’s private lives, including with whom they communicate, whether they have particular medical conditions, or specific locations they have traveled to over a period of time. Although courts generally require police to obtain a warrant before they obtain the contents of people’s communications, law enforcement can obtain a wealth of other information without a warrant.

    The lawmakers’ call for widespread reforms is a welcome development, as too often federal courts across the country keep these records under seal, including even basic docketing information that would only reveal the bare fact that the government applied for a court order to conduct surveillance. This has the effect of making the surveillance largely invisible to the public, journalists, researchers, and academics.

    Beyond calling for better aggregated reporting on these requests, the letter, addressed to the administrative body that oversees all federal courts, also calls on courts to begin to create public versions of their surveillance order dockets. The proposal would give the public access while preserving the secrecy around underlying orders, including the name of the individual and the service provider, when necessary. The letter also calls on courts to limit how long any particular case can be sealed to 180 days to prevent the files from becoming indefinitely sealed and falling down a memory hole.

    “The courts must embrace serious transparency reforms so that Congress and the American people have the appropriate information in order to conduct effective oversight of surveillance programs and understand the scale of government surveillance,” the letter states.

    EFF has long been concerned with the secrecy that surrounds these types of law enforcement information demands. Surveillance does not always lead to criminal prosecutions or other public proceedings, so secrecy at the initial stages may become permanent. This secrecy not only prevents basic reporting about the volume of these types of demands, it also hides any potential abuse of these powers by law enforcement. And as others have noted, the fact that these cases are sealed prevents any meaningful review of whether the surveillance powers are constitutional.

    This is why EFF has fought back against such secrecy, including recently filing a case on behalf of The Stranger in Seattle to unseal federal court records in Washington State.

    EFF thanks Sen. Wyden for his leadership, and we hope that federal courts embrace the letter’s proposals so that the public can finally get a clear picture of the type of surveillance being authorized by those courts.

    Related Cases: The Stranger Unsealing


 



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]
  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:

    lsblk

    Output:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s

    Fin!

    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more
});