Don’t Reauthorize NSA Spying in a Must-Pass Funding Bill
Drudge Bot last edited by
The next two weeks will be a flurry of activity in Congress. Before they can leave for the holidays, our government must—at minimum—pass at least one bill to keep the government running and also decide what to do about a controversial NSA spying authority called Section 702. Some legislators want to reauthorize Section 702, without meaningful reform, by attaching it to must-pass spending legislation. This is a terrible idea. The legislative process surrounding Section 702 already lacks necessary transparency and deliberation.
The new legislative stratagem gets complicated very quickly. Here’s what you need to know.
On December 8<sup>th</sup>, Congress passed a temporary funding bill, or a “Continuing Resolution” (CR) to keep the government running until December 22. To prevent a government shutdown, Congress must either pass another CR by the new deadline, or ideally, finish writing the final funding bill for the rest of Fiscal Year 2018. This final funding bill is known as “the omnibus.”
Even though the Republican Party controls the House, the Senate,[AS1] and the White House, GOP leadership has struggled to find enough consensus among their members to pass the omnibus. Instead, the government is limping along with a series of short-term CRs while avoiding hard decisions on longer term funding priorities. This constant negotiation on funding between the White House and Congressional leaders from both parties means that there is less time to negotiate other issues, like necessary reforms on Section 702 NSA spying program, which is scheduled to sunset at the end of this month.
Faced with multiple looming deadlines, legislators may be tempted to include Section 702 reauthorization in one of the funding bills. The allure of killing two (or more) birds with one stone often becomes overwhelming this time of year. Instead of taking the time to negotiate and navigate multiple difficult votes on various contentious bills, leadership finds it easier to find a majority only once.
Who will decide to include 702 reauthorization language in the CR?
After consulting with the various Chairmen of Committees of jurisdiction (in this case, the Intelligence and Judiciary Committees), Congressional leadership[IM2] , along with the White House, will decide what will help them get the votes they need.
For example, a member who is not inclined to support a spending bill on its own may decide to vote “yes” on a spending bill that includes language to prohibit the NSA’s controversial “about” searching. Of course, the reverse can also be true, which is why such discussions will happen behind closed doors.
Can anyone stop it?
Yes and no. Individual members or groups of members (often called Caucuses) would have to tell their leadership that they would not vote for any spending package that contains language they don’t like. If the numbers work in their favor, and leadership believes them, this will keep the language out of the bill.
However, leadership may choose to call the members’ bluff. If the language is added over members’ objections, the members can still vote no on the whole bill. But that could cause the bill to fail and shut down the government. Government shutdowns are highly disruptive to many people, and thus politically risky. The members and the leadership take that into consideration. It’s a high-risk game of chicken—with very real and long-term consequences.
Can the language be amended once it is added?
Practically speaking, no. All the language in the CR is carefully negotiated behind closed doors, so leadership does not usually allow any amendments in case something accidentally passes that would cost them votes.
Is there any limit to what language can be included in a CR?
Once again, practically speaking, no.
In theory, no spending bill – CR or omnibus – should contain language that isn’t related to funding the government. Of course, how we fund the government often has policy implications, which is why these bills are often so contentious and so tightly negotiated. For example, earlier this year Rep. Kevin Yoder (R-KS) sponsored language in a funding bill that would prevent law enforcement from using any taxpayer dollars to seize cloud-hosted documents (email, photos, etc) without a warrant. In practice, the policy impact of this language would have been quite similar to the Email Privacy Commutations Act, but Rep. Yoder’s language actually only prohibits funding these actions. Adding language that has nothing to do with government funding at all, like reauthorization of the Section 702 program, does happen, but it is rare.
A CR is even less appropriate than an omnibus as a vehicle to make new policy. As it is designed only to be a temporary, short-term measure, a CR is theoretically only a continuation of current funding levels, with no major funding changes and no major policy changes. In practice, this rule gets waived (at the discretion of the leadership), especially when pushed up against a deadline and when the added language brings in needed votes.
How will we know if or what 702 reauthorization language has been added to the CR?
Follow us on Twitter!
In normal circumstances, all legislation is supposed to be public for at least a day before Congress votes on it. Unfortunately, these are not normal circumstances.
When there is a difficult, tightly negotiated bill and a looming deadline (like with both the CR and Section 702 reauthorization), the House of Representatives may enact something called “martial law,” allowing leadership to move quickly through debate and final passage as soon as they have an agreement - before the media or the public have an opportunity to comment.
EFF is in constant communication with members interested in reforming Section 702, and we’re fighting alongside them to make sure Section 702 reauthorization does not sneak through in the dead of night. We’ll make sure to let you know when we know!
Is This Strategem OK?
No! While the legislative calendar may pose a challenge, it is completely unacceptable for Congressional leadership to shove Section 702 reauthorization into an end-of-year funding bill. This program invades the privacy of an untold number of Americans. Before it can be reauthorized, Congress must undertake a transparent and deliberative process to consider the impact this NSA surveillance has on Americans’ privacy.
It is troubling that a secretive NSA surveillance program may be reauthorized in a secret legislative backroom deal. But this program is too important to be hidden in a big funding bill, and members shouldn’t be forced to choose between shutting down the federal government or violating the Fourth Amendment.
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
Recreate postrgresql database template encode to ASCIIUPDATE 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;