Posts

Mueller Would Not Have Needed a Foreign Intelligence Agency to Geolocate Michael Cohen’s Phone

The same McClatchy team that has long been chasing the Steele dossier allegation that Michael Cohen was in Prague in (the first two reports said) August or maybe (the last report said) September has a new story reporting two new details about the allegation, sourced to four people reporting anonymously and secondhand about what “foreign intelligence connections” told them.

I’ll get to the substance of the report in a second, but first I want to point to a claim they make.

If the foreign intelligence intercepts are accurate, the big questions now are whether Cohen has acknowledged to investigators that a meeting in Prague occurred, informed them what transpired and revealed what, if anything, he told Trump about it.

It’s a remarkable claim from reporters trying to cover a part of the Russian investigation (but who have covered very little aside from the Cohen in Prague allegation). Because no, the big questions are not and have not been for some time whether Cohen told investigators of this.

That’s true, in part, because if one of these claims — that Cohen’s phone showed up near Prague in August or maybe September — is true, then Mueller would have had this since April at the latest, and probably significantly earlier. Here’s the allegation:

A mobile phone traced to President Donald Trump’s former lawyer and “fixer” Michael Cohen briefly sent signals ricocheting off cell towers in the Prague area in late summer 2016, at the height of the presidential campaign, leaving an electronic record to support claims that Cohen met secretly there with Russian officials, four people with knowledge of the matter say.

Weirdly, the reporters writing up this story show no awareness of whether Mueller has obtained Cohen’s records.

Mueller’s investigators, some of whom have met with Steele, likely also pursued Cohen’s cell phone records. It would be a common early step in such an investigation for a prosecutor to obtain a court warrant for all U.S. and foreign phone company records of key subjects, even those dating back more than 18 months.

Cohen is likely to be one of the five people who had the information from their AT&T phones (or a likely comparable number who probably had information their Verizon phones) obtained back on March 9 in the wake of the Rick Gates plea. In any case, we know that the FBI seized a whole slew of Cohen’s phones on April 9 and were able to fully exploit all of them save an old Blackberry.

So we don’t have to rely on extrapolating from what are often common first steps, because we know that Mueller has already obtained Cohen’s actual phones (to say nothing of his phone records).

If any of Cohen’s phones were in the vicinity of Prague in 2016 — whether August or maybe September — Mueller knew about it when he told Judge William Pauley that,

Cohen provided the SCO with useful information concerning certain discrete Russia-related matters core to its investigation that he obtained by virtue of his regular contact with Company executives during the campaign.

That’s the one description of Cohen’s cooperation that might incorporate covering up for Manafort in August or maybe September 2016. Perhaps a Prague meeting is included in that bullet — as I noted in April, Cohen’s then lawyer avoided addressing the issue (though Lanny Davis, working as a flack yet being employed as a lawyer, claimed repeatedly after April that Cohen had not been in Prague).

If it was, however, Mueller nevertheless chose to focus on Cohen’s lies about a Trump Tower deal in Cohen’s allocution.

The defendant lied to Congress about a business project (the “Moscow Project”) that he worked on during the 2016 presidential campaign, while he served as Executive Vice President at a Manhattan-based real estate company (the “Company”) and as Special Counsel to the owner of the Company (“Individual 1”).

Nor was a Prague meeting described to be among the things that Cohen lied about at his first proffer session so as to avoid conflicting with lies he told Congress (and if Cohen did go to Prague, he would have lied to Congress about that).

This initial meeting with the SCO, on August 7, 2018, was set up at Cohen’s request. In that meeting, Cohen voluntarily provided information relevant to other aspects of the SCO’s ongoing investigation, but when asked questions about the Moscow Project, Cohen provided false answers in what he later explained was an effort not to contradict his congressional testimony.

And Mueller didn’t include Cohen’s claims about Prague in a footnote describing Cohen’s other lies about contacts with Russians.

The defendant, without prompting by the SCO, also corrected other false and misleading statements that he had made concerning his outreach to and contacts with Russian officials during the course of the campaign. For example, in a radio interview in September 2015, the defendant suggested that Individual 1 meet with the President of Russia in New York City during his visit for the United Nations General Assembly. When asked previously about these events, the defendant claimed his public comments had been spontaneous and had not been discussed within the campaign or the Company. During his proffer sessions, the defendant admitted that this account was false and that he had in fact conferred with Individual 1 about contacting the Russian government before reaching out to gauge Russia’s interest in such a meeting. The meeting ultimately did not take place.

None of that rules out the McClatchy report that Cohen was in Prague. If Cohen was in Prague, Mueller might well want to keep that secret.

But thus far, Mueller seems to think that Cohen’s role in brokering a Trump Tower deal (including, per BuzzFeed’s reporting, with a banker tied to GRU, the intelligence agency that carried out the election year operation) was a more important lie than anything that got reported in the Steele dossier.

All of which is to say that I still stand by this post, in which I argue that it’s high time for reporters to stop focusing primarily on whether details of the Steele dossier have proven true (particularly if that’s all you do on the Russian investigation, as it substantially is with these reporters), and instead look to laying out the implications of the conspiracy that Mueller has already provided corroboration of.

There is growing evidence that Trump conspired with Russians in 2016. That evidence, however, comes increasingly from Mueller, not from Christopher Steele.

As I disclosed in July, I provided information to the FBI on issues related to the Mueller investigation, so I’m going to include disclosure statements on Mueller investigation posts from here on out. I will include the disclosure whether or not the stuff I shared with the FBI pertains to the subject of the post

Government Wouldn’t Unseal Michael Cohen’s Warrants because “Many Uncharged Persons Are Named in the Materials”

Back on October 11, the NYT moved to unseal the search warrants targeting Michael Cohen, arguing the search was of utmost public interest. A bunch of other media outlets have since joined in. On October 25, the government responded, laying out a bunch of reasons why the warrants had to remain sealed. First, it described investigative reasons: unsealing warrants might reveal the identities of persons of interest in criminal investigations, might jeopardize cooperating witnesses, might disclose the full range of crimes under investigation, and might reveal what evidence the government had already collected in the investigation.

Courts have recognized numerous different ways in which the disclosure of sealed materials could interfere with an investigation. Search warrant materials often reveal “the identities of persons of interest in criminal investigations.” In re Search Warrant, 2016 WL 7339113, at *4; In Application of the United States for an Order Pursuant to 18 U.S.C. § 2703(d), 707 F.3d 283, 294 (4th Cir. 2013) (citing fact that “documents at issue set forth sensitive nonpublic facts, including the identity of targets and witnesses in an ongoing criminal investigation”). The disclosure of sealed materials could also jeopardize the cooperation of persons in either the particular investigation or in future cases. Amodeo II, 71 F.3d at 1050. And even when some aspect of a criminal investigation is public, disclosure of a detailed affidavit could “disclose to the subjects the full range of potential criminal violations being investigated, the evidence obtained by the United States prior to the searches, and the information which the subjects and other individuals had provided to the United States or had failed or declined to provide.” In re Sealed Search Warrants Issued June 4 and 5, 2008, 08-M-208 (DRH), 2008 WL 5667021, at *4 (N.D.N.Y. July 14, 2008); see also In re Search Warrant for Secretarial Area Outside Office of Gunn (Gunn), 855 F.2d 569, 574 (8th Cir. 1988) (public access outweighed by fact that disclosure would reveal the “nature, scope and direction of the government’s investigation”).

Let’s see: Cooperating witness, check (Cohen first proffered to Mueller on August 7). Crimes under investigation not already identified, check. Lots of evidence co-conspirators don’t know about, check. The other people being investigated … hmmm.

Indeed, the government’s second reason to keep the warrants sealed is to protect the privacy interests of third parties who are named in the search warrant, but not charged. The response stated clearly that “many uncharged individuals and entities are named in the” search warrants and other documents.

And in the specific context of third parties named in search warrant applications, that interest is especially weighty, because “a person whose conduct is the subject of a criminal investigation but is not charged with a crime should not have his or her reputation sullied by the mere circumstance of an investigation.” In re Search Warrant, 2016 WL 7339113, at *4. Moreover, unlike charged defendants, uncharged third parties whose involvement in or association with criminal activity is alleged in search warrant materials may find themselves harmed by the disclosure but without recourse to respond to the allegation. See In re Newsday, Inc., 895 F.2d at 80; Amodeo II, 71 F.3d at 1051.3

Here, as set forth in the Government’s supplemental submission, many uncharged individuals and entities are named in the Materials.

3 The Government has not notified the uncharged third parties that they were named in the Materials, in part because disclosure of that fact to certain of the uncharged third parties would itself impair the ongoing investigation.

Judge William Pauley has not yet ruled and, surprisingly, the press has not yet renewed their request given Cohen’s second guilty plea this week.

But read retrospectively, the government’s filing makes it clear that part of the reason it insisted on keeping the warrants sealed was to hide the other part of the affidavits covering Cohen’s lies to Congress and the underlying conduct. I’d be acutely interested to see how the government responded if they did make a renewed request, as I suspect it is all the more important to keep the materials sealed now.

Suffice it to say, though, that the charges Cohen originally pled to, even the campaign finance charges that implicated Trump and the Trump Organization, don’t implicate “many uncharged individuals.” As I’ll show in a later post, the lies Cohen told to Congress do implicate people beyond Cohen himself.

But the underlying Trump Tower deal itself — that’s where you begin to get into “many uncharged individuals and entities.”

The Section 215 Rap Sheet

Marco Rubio, who is running for President as an authoritarian, claims that “There is not a single documented case of abuse of this program.”

He’s not alone. One after another defender of the dragnet make such claims. FBI witnesses who were asked specifically about abuses in 2011 claimed FBI did not know of any abuses (even though FBI Director Robert Mueller had had to justify FBI’s use of the program to get it turned back on after abuses discovered in 2009).

Comment — Russ Feingold said that Section 215 authorities have been abused. How does the FBI respond to that accusation?

A — To the FBI’s knowledge, those authorities have not been abused.

Though Section 215 boosters tend to get sort of squishy on their vocabulary, changing language about whether this was illegal, unconstitutional, or abusive.

Here’s what we actually know about the abuses, illegality, and unconstitutionality of Section 215, both the phone dragnet program and Section 215 more generally.

Judges

First, here’s what judges have said about the program:

1) The phone dragnet has been reapproved around 41 times by at least 17 different FISC judges

The government points to this detail as justification for the program. It’s worth noting, however, that FISC didn’t get around to writing an opinion assessing the program legally until 10 judges and 34 orders in.  Since Snowden exposed the program, the FISC appears to have made a concerted effort to have new judges sign off on each new opinion.

2) Three Article III courts have upheld the program:

Judges William Pauley and Lynn Winmill upheld the constitutionality of the program (but did not asses the legality of it); though Pauley was reversed on statutory, not constitutional grounds. Judge Jeffrey Miller upheld the use of Section 215 evidence against Basaaly Moalin on constitutional grounds.

3) One Article III court — Judge Richard Leon in Klayman v. Obama — found the program unconstitutional.

4) The Second Circuit (along with PCLOB, including retired Circuit Court judge Patricia Wald, though they’re not a court), found the program not authorized by statute.

The latter decision, of course, is thus far the binding one. And the 2nd Circuit has suggested that if it has to consider the program on constitution grounds, it might well find it unconstitutional as well.

Statutory abuses

1) As DOJ’s IG confirmed yesterday, for most of the life of the phone dragnet (September 2006 through November 2013), the FBI flouted a mandate imposed by Congress in 2006 to adopt Section 215-specific minimization procedures that would give Americans additional protections under the provision (note–this affects all Section 215 programs, not just the phone dragnet). While, after a few years, FISC started imposing its own minimization procedures and reporting requirements (and rejected proposed minimization procedures in 2010), it nevertheless kept approving Section 215 orders.

In other words, in addition to being illegal (per the 2nd Circuit), the program also violated this part of the law for 7 years.

2) Along with all the violations of minimization procedures imposed by FISC discovered in 2009, the NSA admitted that it had been tracking roughly 3,000 presumed US persons against data collected under Section 215 without first certifying that they weren’t targeted on the basis of First Amendment protected activities, as required by the statute.

Between 24 May 2006 and 2 February 2009, NSA Homeland Mission Coordinators (HMCs) or their predecessors concluded that approximately 3,000 domestic telephone identifiers reported to Intelligence Community agencies satisfied the RAS standard and could be used as seed identifiers. However, at the time these domestic telephone identifiers were designated as RAS-approved, NSA’s OGC had not reviewed and approved their use as “seeds” as required by the Court’s Orders. NSA remedied this compliance incident by re-designating all such telephone identifiers as non RAS-approved for use as seed identifiers in early February 2009. NSA verified that although some of the 3,000 domestic identifiers generated alerts as a result of the Telephony Activity Detection Process discussed above, none of those alerts resulted in reports to Intelligence Community agencies.

NSA did not fix this problem by reviewing the basis for their targeting; instead, it simply moved these US person identifiers back onto the EO 12333 only list.

While we don’t have the background explanation, in the last year, FISC reiterated that the government must give First Amendment review before targeting people under Emergency Provisions. If so, that would reflect the second time where close FISC review led the government to admit it wasn’t doing proper First Amendment reviews, which may reflect a more systematic problem. That would not be surprising, since the government has already been chipping away at that First Amendment review via specific orders.

Minimization procedure abuses

1) The best known abuses of minimization procedures imposed by the FISC were disclosed to the FISC in 2009. The main item disclosed involved the fact that NSA had been abusing the term “archive” to create a pre-archive search against identifiers not approved for search. While NSA claimed this problem arose because no one person knew what the requirements were, in point of fact, NSA’s Inspector General warned that this alert function should be disclosed to FISC, and it was a function from the Stellar Wind program that NSA simply did not turn off when FISC set new requirements when it rubber-stamped the program.

But there were a slew of other violations of FISC-imposed minimization procedures disclosed at that time, almost all arising because NSA treated 215 data just like it treats EO 12333, in spite of FISC’s clear requirements that such data be treated with additional protections. That includes making query results available to CIA and FBI, the use of automatic search functions, and including querying on any “correlated” identifiers. These violations, in sum, are very instructive for the USA F-ReDux debate because NSA has never managed to turn these automated processes back on since, and one thing they presumably hope to gain out of moving data to the providers is to better automate the process.

2) A potentially far more egregious abuse of minimization procedures was discovered (and disclosed) in 2012, when NSA discovered that raw data NSA’s techs were using over 3,000 files of phone dragnet data on their technical server past the destruction date.

As of 16 February 2012, NSA determined that approximately 3,032 files containing call detail records potentially collected pursuant to prior BR Orders were retained on a server and been collected more than five years ago in violation of the 5-year retention period established for BR collection. Specifically, these files were retained on a server used by technical personnel working with the Business Records metadata to maintain documentation of provider feed data formats and performed background analysis to document why certain contact chaining rules were created. In addition to the BR work, this server also contains information related to the STELLARWIND program and files which do not appear to be related to either of these programs. NSA bases its determination that these files may be in violation of BR 11-191 because of the type of information contained in the files (i.e., call detail records), the access to the server by technical personnel who worked with the BR metadata, and the listed “creation date” for the files. It is possible that these files contain STELLARWIND data, despite the creation date. The STELLARWIND data could have been copied to this server, and that process could have changed the creation date to a timeframe that appears to indicate that they may contain BR metadata.

But rather than investigate this violation — rather than clarify how much data this entailed, whether it had been mingled with Stellar Wind data, whether any other violations had occurred — NSA destroyed the data.

In one incident, NSA technical personnel discovered a technical server with nearly 3,000 files containing call detail records that were more than five years old, but that had not been destroyed in accordance with the applicable retention rules. These files were among those used in connection with a migration of call detail records to a new system. Because a single file may contain more than one call detail record, and because the files were promptly destroyed by agency technical personnel, the NSA could not provide an estimate regarding the volume of calling records that were retained beyond the five-year limit. The technical server in question was not available to intelligence analysts.

From everything we’ve seen the tech and research functions are not audited, not even when they’re playing with raw data (which is, I guess, why SysAdmin Edward Snowden could walk away with so many records). So not only does this violation show that tech access to raw data falls outside of the compliance mechanisms laid out in minimization procedures (in part, with explicit permission), but that NSA doesn’t try very hard to track down very significant violations that happen.

Overall sloppiness

Finally, while sloppiness on applications is not a legal violation, it does raise concerns about production under the statute. The IG Report reviewed just six case files which used Section 215 orders. Although the section is heavily redacted, there are reasons to be significantly concerned about four of those.

  • An application made using expedited approval that made a material misstatement about where FBI obtained a tip about the content of a phone call. The FBI agent involved “is no longer with the FBI.” The target was prosecuted for unlawful disclosure of nuke information, but the Section 215 evidence was not introduced into trial and therefore he did not have an opportunity to challenge any illegal investigative methods.
  • A 2009 application involving significant minimization concerns and for which FBI rolled out a “investigative value” exception for access limits on Section 215 databases. This also may involve FBI’s secret definition of US person, which I suspect pertains to treating IP addresses as non-US persons until they know it is a US person (this is akin to what they do under 702 MPs). DOJ’s minimization report to FISC included inaccuracies not fixed until June 13, 2013.
  • A 2009 application for a preliminary investigation that obtained medical and education records from the target’s employer. FBI ultimately determined the target “had no nexus to terrorism,” though it appears FBI kept all information on the target (meaning he will have records at FBI for 30 years). The FBI’s minimization report included an error not fixed until June 13, 2013, after the IG pointed it out.
  • A cyber-investigation for which the case agent could not locate the original production, which he claims was never placed in the case file.

And that’s just what can be discerned from the unredacted bits.

Remember, too: the inaccuracies (as opposed to the material misstatement) were on minimization procedures. Which suggests FBI was either deceitful — or inattentive — to how it was complying with FISC-mandated minimization procedures designed to protect innocent Americans’ privacy.

And remember — all this is just Section 215. The legal violations under PRTT were far more egregious, and there are other known violations and misstatements to FISC on other programs.

This is a troubling program, one that several judges have found either unconstitutional or illegal.

 

NSA’s Latest Claim: It Only Gets 30% of “Substantially All” the Hay in the Haystack

SIGINT and 215In December 2007, the FBI began intercepting MOALIN’s cell phone.

FBI search warrant affidavit seeking (among other things) additional cell phones, October 29, 2010

Yesterday, Siobhan Gorman reported that NSA’s “phone-data program” collects 20% or less of the phone data in the US. She explains that the program doesn’t collect cell phone data, and so has covered a decreasing percentage of US calls over the last several years.

The National Security Agency’s phone-data program, which has been at the center of controversy over the NSA’s surveillance operations, collects information from about 20% or less of all U.S. calls—much less than previously described by lawmakers.

The program had been described as collecting records on virtually every phone call placed in the U.S., but in fact, it doesn’t cover records for most cellphones, the fastest-growing sector in telephony and an area where the agency has struggled to keep pace, according to several people familiar with the program.

Ellen Nakashima’s report places the percentage between 20 and 30%, echoing Gorman’s claim about limits on cell data.

The actual percentage of records gathered is somewhere between 20 and 30 percent and reflects Americans’ increasing turn away from the use of land lines to cellphones. Officials also have faced technical challenges in preparing the NSA database to handle large amounts of new records without taking in data such as cell tower locations that are not authorized for collection.

[snip]

The bulk collection began largely as a land-line program, focusing on carriers such as AT&T and Verizon Business Network Services. At least two large wireless companies are not covered — Verizon Wireless and T-Mobile U.S., which was first reported by the Wall Street Journal.

Industry officials have speculated that partial foreign ownership has made the NSA reluctant to issue orders to those carriers. But U.S. officials said that was not a reason.

“They’re doing business in the United States; they’re required to comply with U.S. law,” said one senior U.S. official. “A court order is a court order.”

Rather, the official said, the drop in collection stems from several factors.

Apart from the decline in land-line use, the agency has struggled to prepare its database to handle vast amounts of cellphone data, current and former officials say. For instance, cellphone records may contain geolocation data, which the NSA is not permitted to receive.

These reports offer a more credible explanation than Geoffrey Stone’s multiple claims to this effect about why the program misses data. So they may be true.

But I think they instead point to the legal range of authorities NSA uses to collect phone records, not to what records they actually have in their possession.

These reports are commenting (though without specifying, or even seeming to be aware they need to specify) on what the government claims it collects under Section 215. These reports are not commenting on what NSA collects under all authorities.

In this post I will show why I believe these reports to be credible only in a very narrow sense. In a follow-up post I will point to the legal issues that underlie the Administration’s conflicting claims about what it collects.

Read more

Judge Pauley’s Deliberate Blind Spot: Systematic Section 215 Abuses

Sorry for my silence of late, particularly regarding William Pauley’s ruling finding the phone dragnet legal. The good news is my mom can now reach the light switch in her sewing room without risk of falling.

As noted, Judge Pauley ruled against the ACLU in their suit challenging the phone dragnet. A number of commentators have pointed to some bizarre errors or focus in Pauley’s ruling, including,

  • Pauley says the government could not find the “gossamer threads” of terrorist plotters leading up to 9/11. They did find them. They simply didn’t act appropriately with them.
  • He unquestioningly considers the 3 uses of Section 215 (with Zazi, Headley, and Ouazzani) proof that it is effective. He does not note that even Keith Alexander has admitted it was only critical in one case, one not even mentioned in the government’s filings in this case.
  • He ignores the role of the Executive in willingly declassifying many details this program, instead finding it dangerous to allow the ACLU to sue based on an unauthorized leak. The government has actually been very selective about what Snowden-leaked programs they’ve declassified, almost certainly to protect even more problematic programs from legal challenge.
  • He claims Congress has renewed Section 215 7 times (including 2001, it was renewed it 5 times).
  • He claims there is no doubt the Intelligence and Judiciary Committees knew about the rulings underlying the program in spite of the fact that some rulings were not provided until after Section 215 was renewed; he admits that the limits on circulation of notice in 2011 was “problematic” but asserts the Executive met its statutory requirements (he doesn’t deal with the evidence in the record that the Executive Branch lied in briefings about the conduct of the dragnet).

There are also Pauley’s claims about the amount of data included — he says the government collects all phone metadata; they say NSA collects far less data. This is a more complicated issue which I’ll return to, though maybe not until the New Year.

But I’m most interested in the evidence Pauley points to to support his claim that the FISC (and Congress) conduct adequate oversight over this program. He points to John Bates’ limits to the government’s intentional collection of US person data via upstream collection rather than Reggie Walton’s limits to Section 215 abuses.

For example, in 20011, FISC Judge Bates engaged in a protracted iterative process with the Government–over the Government’s application for reauthorization of another FISA collection program. That led to a complete review of that program’s collection and querying methods.

He then immediately turns to Claire Eagan’s opinion reiterating that the government had found and dealt with abuses of the phone dragnet program.

In other words, for some bizarre reason he introduces a series of rulings pertaining to Section 702 — and not to Section 215 — to support his argument that the government can regulate this Section 215 collection adequately.

It’s particularly bizarre given that we have far more documents showing the iterative process that took place in 2009 pertaining directly to the phone dragnet. Why even mention the Bates rulings on upstream collection when there are so many Reggie Walton ones pertaining directly to Section 215?

I suspect this is because Pauley relies so heavily on the adequacy of the minimization procedures imposed by the FISC, as when he cites Claire Eagan’s problematic opinion to claim that without adequate minimization procedures, FISC would not approve Section 215 phone dragnet orders.

Without those minimization procedures, FISC would not issue any section 215 orders for bulk telephony metadata collection.

(Note, Pauley doesn’t note that the government has not met the terms of the Section 215 itself with regards to minimization procedures, which among other things would require an analysis of the NSA using a statute written for the FBI.)

The only way Pauley can say the limits he points to in his analysis — that NSA can only analyze 3 hops deep, that FBI only gets summaries of the queries, that every query got approved for RAS — is if he ignores that for the first 3 years of the program, all of these claims were false.

He uses similar analysis to dismiss concerns about the power of metadata.

But [ACLU’s contention that the government could use metadata analysis to learn sensitive details about people] is at least three inflections from the Government’s bulk telephony metadata collection. First, without additional legal justification–subject to rigorous minimization procedures–the NSA cannot even query the telephony metadata database. Second, when it makes a query, it only learns the telephony metadata of the telephone numbers within three “hops” of the “seed.” Third, without resort to additional techniques, the Government does not know who any of the telephone numbers belong to.

These last assertions are all particularly flawed. Not only have these minimization procedures failed in the past, not only has the government been able to go four hops deep in the past (which could conceivably include all Americans in a query), not only is there abundant evidence — which I’ll lay out in a future post — that the government does know the identities of at least some of those whom it is chaining, but there are two ways the government accesses this data for which none of this is true: when “data integrity analysts” fiddle with the data to prepare it for querying, and when it is placed in the “corporate store” and analyzed further.

All the claims about minimization Pauley uses to deem this program legal have big big problems.

The NSA conducted a fraud on the FISC for 3 years (and still is, to the extent they claim the violations under the program arose from complexity rather than their insistence on adopting all the practices used under the illegal program for the FISC-authorized program). Yet Pauley points to the FISC to dismiss any Constitutional concerns with this program.

And to do that, he ignores the abundant evidence that all his claims have been — and may still be, in some cases — false.