Posts

John Bolton Versus Navy Versus Egan

John Bolton filed a motion opposing the government’s legal actions against him last night (it is both a memorandum in opposition to the Temporary Restraining Order as well as a motion to dismiss). It is particularly interesting because of some things Jack Goldsmith and Marty Lederman laid out in this post. As they note, the judge presiding over today’s hearing has no tolerance for Executive Branch bullshit, even on classified matters; the government’s own description of what happened raises lots of questions about regularity of the claim of classification, particularly as respects to whether there any compartmented information (SCI) remains in Bolton’s book; and the scrutiny of the government will be particularly stringent here, since it wants to censor something before publication.

This, however, might be a case in which a judge rejects or at least refuses to countenance the government’s classification decisions, at least for purposes of the requested injunction. That’s because of a confluence of unusual factors.  They include:

  • Several years ago, Judge Lamberth declared at a conference of federal employees that federal courts are “far too deferential” to the executive branch’s claims that certain information must be classified on national security grounds and shouldn’t be released to the public.  Judges shouldn’t afford government officials “almost blind deference,” said Lamberth.
  • The decision to classify material here appears to be highly irregular.  The career official responsible for prepublication review at the National Security Council determined after a long process that Bolton’s manuscript contained no classified information.  A political appointee who had only recently become a classifying authority, Ellis, then arrived at a different conclusion after only a brief review.  It is even possible that Ellis classified information in Bolton’s manuscript for the first time after Bolton was told by Knight that the manuscript contained no classified information.  At a minimum there were clearly process irregularities in the prepublication consideration of Bolton’s manuscript.
  • The D.C. Circuit in dicta in McGehee stated that the government “would bear a much heavier burden” than the usual rationality review of executive branch classified information determinations in cases where the government seeks “an injunction against publication of censored items”—i.e., in a case like this one.  Although it’s not clear whether that’s right, the First Amendment concerns raised by this case, in this setting, may affect how credulous Judge Lamberth is of the government’s classified information determinations and of the unusual way in which Bolton’s prepublication review was conducted.

Bolton’s motion answers a lot of questions that Goldsmith and Lederman asked in their post. For example, they ask whether Ellen Knight consulted with other top classification authorities before she verbally told Bolton the book had no more classified information in it; Bolton’s motion describes that on the call when Knight told Bolton the book had no more classified information, she, “cryptically replied that her ‘interaction’ with unnamed others in the White House about the book had ‘been very delicate,’ and that there were ‘some internal process considerations to work through.'”

Goldsmith and Lederman lay out a lot of questions contemplating the likelihood that Michael Ellis claimed the manuscript had SCI information after Knight informed Bolton that it had no more classified information, of any kind (remember, Ellis is likely the guy who moved Trump’s Ukraine transcript onto the compartmented server after people started raising concerns about it, so there would be precedent). Bolton’s brief lays out an extended description of why, if this indeed happened, it doesn’t matter with respect to the way his SCI non-disclosure agreement is written, because based on the record even the government presents, Bolton had no reason to believe the manuscript had SCI in it, and plenty of reason to believe it had no classified information of any type, when he instructed Simon & Schuster to move towards publication.

However, in its brief, the Government asserts for the first time that Ambassador Bolton’s book contains SCI and, therefore, that the SCI NDA applied to his manuscript and required that he receive written authorization from the NSC to publish it. See Doc. 3 at 12–14. This surprise assertion that the book contains SCI, even if true, would not alter the conclusion that the SCI NDA is inapplicable to this case.

The Government is not painting on a blank canvas when it asserts that Ambassador Bolton’s book contains SCI. Rather, the Government’s assertion comes after a six-month course of dealing between the parties that informs whether and how the NDAs apply. See RESTATEMENT (SECOND) OF CONTRACTS § 202(4) (1981); see also id. § 223. Ambassador Bolton submitted his manuscript for prepublication review on December 30, 2019. Over the next four months, he (or his counsel) and Ms. Knight exchanged more than a dozen emails and letters, participated in numerous phone calls, and sat through more than a dozen hours of face-to-face meetings, painstakingly reviewing Ambassador Bolton’s manuscript. Yet, in all that time, Ms. Knight never asserted—or even hinted—that the manuscript contained SCI, even as she asserted that earlier drafts contained classified information. 102 After conducting an exhaustive process in which she reviewed the manuscript through least four waves of changes, Ms. Knight concluded that it contains no classified information—let alone SCI—as the Government concedes. Doc. 1 ¶ 46.

Nor did Mr. Eisenberg assert in either his June 8 or June 11 letters that the manuscript contains SCI. Nor did Mr. Ellis assert in his June 16 letter that the manuscript contains SCI. Indeed, not even the Government’s complaint asserted that the manuscript contains SCI, even as it specifically alleges that it contains “Confidential, Secret, and Top Secret” information. Doc. 1 ¶ 58. The first time that anyone in the Government so much as whispered that the manuscript contains SCI to either Ambassador Bolton or the public was yesterday, when the Government filed its motion. For nearly six months, it has been common ground between the NSC and Ambassador Bolton that his manuscript does not contain SCI. Only now, on the eve of the book’s publication and in service of seeking a prior restraint, has the Government brought forth this allegation.

And here is the key point: Ambassador Bolton authorized Simon & Schuster to publish his manuscript weeks ago, not long after receiving Ms. Knight’s confirmation that the book did not contain classified information and long before the Government’s first assertion yesterday that the book contained SCI. 103 Thus, at the time Ambassador Bolton proceeded with publishing his book—a decision that has long-since become irrevocable—he had absolutely no reason to believe that the book contained SCI. Indeed, quite the opposite: the Government had given him every reason to believe that it agreed with him that the book did not contain SCI. And if the book did not contain SCI, the SCI NDA did not apply when Ambassador Bolton authorized the book’s publication.

Yet the Government now argues that the SCI NDA did apply based on its discovery of alleged SCI six months after the prepublication-review process began. If that argument is sustained—if, that is, an author may be held liable under the SCI NDA even though neither the author nor the Government believed that the author’s writing contained SCI through four months of exhaustive prepublication review—it would mean that any federal employee who signs the SCI NDA would have no choice but to submit any writing, and certainly any writing that could even theoretically contain SCI, and then await written authorization before publishing that writing. The risk of liability would simply be too great for any author to proceed with publishing even a writing that both he and the official in charge of prepublication review believe, in good faith, is not subject to the SCI NDA.

What Goldsmith and Lederman don’t address — but Bolton does at length in his brief — is the role of the President in these matters. Bolton lays out (as many litigants against the President have before) abundant evidence that the President was retaliating here, including by redefining as highly classified any conversation with him at a very late stage in this process.

Yet, the evidence is overwhelming that the Government’s assertion that the manuscript contains classified information, like the corrupted prepublication review process that preceded it, is pretextual and in bad faith:

  • On January 29, the President tweeted that Ambassador Bolton’s book is “nasty & untrue,” thus implicitly acknowledging that its contents had been at least partially described to him. He also said that the book was “All Classified National Security.”112
  • On February 3, Vanity Fair reported that the President “has an enemies list,” that “Bolton is at the top of the list,” and that the “campaign against Bolton” included Ms. Knight’s January 23 letter asserting that the manuscript contained classified information.113 It also reported that the President “wants Bolton to be criminally investigated.”114
  • On February 21, the Washington Post reported that “President Trump has directly weighed in on the White House [prepublication] review of a forthcoming book by his former national security adviser, telling his staff that he views John Bolton as ‘a traitor,’ that everything he uttered to the departed aide about national security is classified and that he will seek to block the book’s publication.”115 The President vowed: “[W]e’re going to try and block the publication of [his] book. After I leave office, he can do this.”116
  • As described in detail above, Ambassador Bolton’s book went through a four-month prepublication-review process with the career professionals at NSC, during which he made innumerable revisions to the manuscript in response to Ms. Knight’s concerns. At the end of that exhaustive process, she stated that she had no further edits to the manuscript,117 thereby confirming, as the Government has admitted, that she had concluded that it did not contain any classified information.118
  • At the conclusion of the prepublication-review process on April 27, Ms. Knight thought that Ambassador Bolton was entitled to receive the pro-forma letter clearing the book for publication and suggested that it might be ready that same afternoon.119 She and Ambassador Bolton even discussed how the letter should be transmitted to him.120
  • During that same April 27 conversation, Ms. Knight described her “interaction” with unnamed others in the White House about the book as having “been very delicate,”121 and she had “some internal process considerations to work through.”
  • After April 27, six weeks passed without a word from the White House about Ambassador Bolton’s manuscript, despite his requests for a status update.122
  • When the White House finally had something new to say, it was to assert its current allegations of classified information on June 8, in a letter that—by the White House’s own admission—was prompted by press reports that the book was about to be published.123
  • Even though the manuscript was submitted to NSC on December 30, 2019, and despite the exhaustive four-month review and the six weeks of silence that had passed since Ms. Knight’s approval of the manuscript on April 27, the White House’s June 8 letter gave itself until June 19—only four days before the book was due to be published—to provide Ambassador Bolton’s counsel with a redacted copy of the book identifying the passages the White House purported to believe were classified.
  • On the eve of this lawsuit being filed, in response to a question about this lawsuit, the President stated: “I told that to the attorney general before; I will consider every conversation with me as president highly classified. So that would mean that if he wrote a book, and if the book gets out, he’s broken the law.”124 The President reiterated: “Any conversation with me is classified.”125 The President added that “a lot of people are very angry with [Bolton] for writing a book” and that he “hope[d]” that Ambassador Bolton “would have criminal problems” due to having published the book.126
  • On June 16, the NSC provided to Ambassador Bolton a copy of the manuscript with wholesale redactions removing the portions it now claims are classified. Consistent with President Trump’s claim, statements made by the President have been redacted, as have numerous passages that depict the President in an unfavorable light.127

It is clear from this evidence that the White House has abused the prepublication-review and classification process, and has asserted fictional national security concerns as a pretext to censor, or at least to delay indefinitely, Ambassador Bolton’s right to speak.

While Goldsmith and Lederman focused, with good reason, on Ellis’ role, Bolton is focused on President Trump’s role. Bolton lays out abundant evidence that the reason this prepublication review went off the rails is because the President, knowing how unflattering it was to him, made sure it did.

And that raises entirely new issues because under a SCOTUS precedent called Navy v. Egan, the Executive has long held that the President has unreviewable authority over classification and declassification decisions. That doesn’t change contract law. And–given that the courts have already granted the President a limited authority to protect the kinds of things being called SCI here under Executive Privilege–it raises real questions about whether Trump is relying on the proper legal claim here (which may be a testament to the fact that Executive Privilege holds little sway over former government officials).

Still, courts have sanctioned a bunch of absurdity about classification under the Navy v. Egan precedent, arguably far beyond the scope of what that decision (which pertained to clearances) covered. Yet, I would argue that Bolton has made Navy v. Egan a central question (though he does not mention it once) in this litigation.

Can the President retroactively classify information as SCI solely to retaliate against someone for embarrassing him — including by exposing him to criminal prosecution under the Espionage Act? That’s the stuff of tyranny, and Royce Lamberth is not the judge who’ll play along with it.

Let me very clear however, particularly for the benefit of some frothy leftists who are claiming — in contradiction to all evidence — that liberals are somehow embracing Bolton by criticizing Trump’s actions here: Bolton’s plight is not that different from what whistleblowers claim happens to them when they embarrass the Executive Branch generally. Their books get held up in review and some of them get prosecuted under the Espionage Act.

What makes this more ironic, involving Bolton, is that he has been on the opposite side of this issue. Indeed, the Valerie Plame leak investigation focused closely on whether Dick Cheney’s orders to Scooter Libby to leak classified information — after which he leaked details consistent with knowing Plame’s covert status, as well as details from the National Intelligence Estimate — were properly approved by George Bush. Bolton was a party to that pushback and his deputy Fred Fleitz was suspected of having had a more active role in it. In that case, the President (or Vice President) retaliated for the release of embarrassing information by declassifying information for political purposes. But in that case, the details of what the President had done have remained secret, protected by Libby’s lies to this day.

In this case, Bolton can present a long list of evidence — including the President’s own statements — that suggest these classification decisions were retaliatory, part of a deliberate effort to trap Bolton in a legal morass.

So Bolton isn’t unique for his treatment as a “whistleblower” (setting aside his cowardice in waiting to say all this). He’s typical. What’s not typical is how clearly the President’s own role and abusive intent is laid out. And because of the latter fact — because, as usual, Trump hasn’t hidden his abusive purpose — it may more directly test the limits of the President’s supposedly unreviewable authority to classify information. So, ironically, someone like Bolton may finally be in a position to test whether Navy v. Egan really extends to sanctioning the retroactive classification of information solely to expose someone to criminal liability.

Stealing Elections: The Underlying Assumption behind Billy Barr’s Flip-Flop on the Materiality of Flynn’s Lies

Marty Lederman has a very long piece assessing DOJ’s motion to dismiss the Mike Flynn case, one that pulls together a lot of the public record (including details, like about DOJ’s January 24, 2017 sentencing memorandum, that haven’t gotten attention other than at this site). As a very sober assessment that criticizes the FBI but lays out the national security implications, it’s well worth reading.

Even after he wades through all those details, though, Lederman argues that the important takeaway isn’t whether Flynn will do prison time or not (he notes, as I have, that Flynn will be pardoned in any case), but instead what this incident says about Bill Barr.

Unfortunately, just as with the public’s anticipation of and reaction to the Mueller investigation, the inordinate focus on whether a particular individual committed one or another offense under the U.S. criminal code is diverting attention from where it ought to be, on much more significant matters of constitutional governance.

Most importantly, as I’ll explain, what’s most alarming and troubling about the DOJ brief itself is not that it asks the court for leave to dismiss the charge against Flynn, but that it depends upon the rather shocking view of the Attorney General and the Acting U.S. Attorney for the District of Columbia that Flynn’s underlying conduct in 2016 and 2017 was unobjectionable and that therefore there wasn’t a “legitimate” basis for the FBI to be investigating Flynn’s secret communications with the Russian Ambassador at all, even though Russia had just completed an elaborate effort to manipulate the American electoral process in order to help elect Donald Trump.

[snip]

There is, however, at least one other possibility—one that’s much more troubling but that doesn’t involve prosecutorial “bad faith,” as such:  It could be, as Charlie Savage recently put it, that Attorney General Barr sincerely “considers to be illegitimate the government’s counterintelligence effort to understand the scope of Russian election interference in 2016 and any links to the Trump campaign.”  That would explain the astounding assertions in the DOJ motion that Flynn’s calls with Kislyak “were entirely appropriate on their face” and that there wasn’t any “legitimate” basis for a counterintelligence investigation, even after Flynn lied to the Vice-President-Elect about the content of the calls.  Indeed, in a recent interview, Attorney General Barr asserted that the FBI investigation was “based on a perfectly legitimate and appropriate call [Flynn] made as a member of the transition.”  According to Barr, there “was nothing wrong with it whatever. In fact, it was laudable.”

If that’s the reason Barr insisted on moving to dismiss the Flynn charge, it raises a far, far greater problem than whether Michael Flynn is or isn’t convicted of a criminal offense.  Such a view reflects an alarming disregard for the constitutional difference between an incumbent President and the incoming administration.  It ignores the harms of engaging in such private diplomacy in secret, without the knowledge of the State Department.  It treats as “laudable” an effort to undermine the incumbent President’s conduct of foreign affairs in real time—and to do so in order to accommodate a hostile nation that had just engaged in a concerted effort to distort the U.S. presidential campaign in order to secure the election of the very President whose agent is engaged in the stealth diplomacy, and where that very President (and/or his agent engaged in the shadow communications) might possibly be in debt to that nation, and/or compromised by it.  It also assumes that the FBI should have turned a blind eye to all this even after several top officials of the new administration made repeated false representations to the public about the new National Security Advisor’s communications with that foreign power, either knowing that the statements were false or, more troubling still, having been assured by Flynn that the communications were very different from what the Bureau knew them to be.  If the Attorney General of the United States believes all of that conduct was “legitimate,” “appropriate” and “laudable,” and that there wasn’t any “legitimate” basis for investigating it, then how can anyone be confident that the Department of Justice under his stewardship will faithfully fulfill its constitutional responsibilities?

I think Lederman is right: Even more than the question of whether Flynn does time is the question of what it means that Barr intervened and — based off no new evidence — weighed in to say that it was laudable that Flynn called up Russia and undermined the punishment Obama imposed after Russia tampered in the election and illegitimate for FBI to investigate why he did so (predictably, the motion to dismiss doesn’t deal with Flynn’s work for Turkey).

But I would go further.

Lederman is rightly offended that Bill Barr has just given sanction to undermining the constitutional transition between one administration and another.

But that’s not all that the FBI was investigating, nor is it what the record suggests Barr is sanctioning.

In his post, Lederman suggests the FBI didn’t take any of the logical steps to chase down Flynn as a counterintelligence concern.

As I hoped I’ve shown above, that was precisely correct—the principal objective of any interview with Flynn should have been to get to the bottom of the potential counterintelligence threat.  FBI Director Comey himself later testified that he sent his agents to interview Flynn on January 24, 2017 at least in part because there was a “disconnect” between what the Vice President was saying in public and what Flynn had in fact said to Kislyak, and Comey wanted his agents “to sit before [Flynn] and say ‘what is the deal?’”  And FBI Counterintelligence Chief Bill Priestap apparently agreed.  His notes from that morning state his view that “if [Flynn] initially lies, then we present him [redacted] and he admits it, document for DOJ, and let them decide how to address it.”

As far as the available public record shows, however, the agents who interviewed Flynn didn’t take that route.  Instead, it appears that Bureau leadership apparently decided before the interview that if Flynn didn’t confirm to the agents what they knew he had said to Kislyak, “they would not confront him or talk him through it.”  (The quote is from a later 302 report of an interview with one of the agents, Peter Strzok.  Unfortunately, the reasons for that decision appear to be redacted from Strzok’s 302 Report.  Nor is it clear who made this tactical decision.)  In the interview itself, Flynn said he couldn’t recall any discussion with Kislyak of the sanctions and expulsions, even after the agents used his own words from those conversations in order to jog his memory (and/or to subtly signal to him that they had a recording).  And then the agents left it at that.  They didn’t confront Flynn with evidence of what he had said to Kislyak; didn’t ask him why he said such things; about who else, if anyone, he discussed the call with, before or after; why he had disregarded the Obama administration’s pointed request that he not have such conversations; why he had lied to Pence, et al.; etc.  In other words, they didn’t do any of the things one might expect investigators to do if their goal was to get to the bottom of the case, and assess the scope and degree of any possible counterintelligence threat, during that interview.  Instead, all they appeared to accomplish was to confirm that Flynn was committed to lying about his calls with Kislyak.

This is the one part of Lederman’s post that I believe is wrong.

On January 24, 2017, the FBI would have learned that Flynn was going to continue to lie about his discussion of sanctions. But the evidence would still have supported an interpretation that Flynn had gone rogue, that he — someone who had been paid directly by Russia in the previous year and met directly with Putin — had decided to undermine all of US policy in response to the Russian operation all by himself.

That interpretation would change.

Moreover, the record shows the FBI did take next steps, but next steps that served to get at the key purpose for Flynn’s lies, to hide that he had consulted with Mar-a-Lago before calling Kislyak. As I have laid out here, the FBI did some call records analysis (on Flynn’s private phone, because he hadn’t used his government issue BlackBerry). That would have disclosed a bunch of calls to Mar-a-Lago beforehand, calls that were clearly inconsistent with Flynn’s claims to the FBI. Ultimately, FBI obtained the devices that first Flynn, and then other members of the Transition had used. Those would show emails explicitly discussing strategy on sanctions. Between getting those communications and getting Flynn to flip, FBI would eventually have gotten KT McFarland to tell her version of the story.

After a year of work, the FBI would have substantiated that Flynn’s lies served to hide his consultation with Mar-a-Lago. Mueller never got him or McFarland or Steve Bannon to admit that Trump weighed in ahead of time (and Mueller was deliberately coy about whether he has phone records suggesting he did).

Ultimately, though, Mueller was never able to answer a key question: whether Trump had ordered Flynn to do what he did.

Although transition officials at Mara-Lago had some concern about possible Russian reactions to the sanctions, the investigation did not identify evidence that the President-Elect asked Flynn to make any request to Kislyak.

As Lederman himself notes, Trump blew off questions about his role in all of this when asked.

Although it’s therefore almost certain Trump knew at least roughly what Flynn planned to say to Kislyak, the Mueller investigation did not find any evidence that Trump directed Flynn to say anything about sanctions.  (Mueller asked Trump specifically about these incidents (see Questions V(b)-(e)), but in his written responses the President … simply ignored those questions, as though they hadn’t even been asked.)  Several weeks later, then-President Trump said in a press conference that although he didn’t direct Flynn to discuss sanctions with Kislyak, “it certainly would have been okay with me if he did.  I would have directed him to do it if I thought he wasn’t doing it. I didn’t direct him, but I would have directed him because that’s his job.”

And Lederman notes the part of the January sentencing memo that describes how central a question sanctions were to Mueller’s investigation.

In a sentencing memorandum it filed in January 2020, the Department of Justice explained that after Flynn’s calls with Kislyak and the false stories that Pence and others were purveying, the FBI “did not know the totality of what had occurred between the defendant and the Russians,” and that “determining the extent of [Flynn’s] actions, why [he] took such actions, and at whose direction he took those actions, were critical to the FBI’s counterintelligence investigation.”  This was particularly true because “[a]ny effort to undermine the recently imposed sanctions, which were enacted to punish the Russian government for interfering in the 2016 election, could have been evidence of links or coordination between the Trump Campaign and Russia.”

What he doesn’t consider, however (though he comes awfully close), is the aspect of Mueller’s investigation that considered whether there was a quid pro quo.

In particular, the investigation examined whether these contacts involved or resulted in coordination or a conspiracy with the Trump Campaign and Russia, including with respect to Russia providing assistance to the Campaign in exchange for any sort of favorable treatment in the future. Based on the available information, the investigation did not establish such coordination.

That is, Mueller wasn’t just investigating whether Trump was friendly to Russia because he was friendly to Russia or whether he was friendly to Russia out of tacit acknowledgement that Russia had helped him.

Mueller was also investigating (and parts of DOJ may still be investigating) whether Trump entered into one or more quid pro quos in which he accepted help getting elected in exchange for implicit or explicit pay-offs later.

Whether or not Mueller proved a quid pro quo (and there are aspects of this that remain ongoing, or recently were ongoing before Barr’s latest efforts to undermine them), that was an obvious, legitimate topic for investigation after a campaign advisor got approached about Russia’s help in April and after Trump asked Russia for help in the same press appearance where he offered to recognize Russia’s annexation of Crimea.

That’s what FBI’s investigation ultimately became. That’s the question the answer to which Flynn’s lies about consulting with Mar-a-Lago have obscured. That is the part of the investigation that Flynn’s lies had a material impact on.

Bill Barr is saying it was illegitimate for the FBI to investigate whether the incoming President engaged in a quid pro quo to get elected and therefore Flynn’s lies that hid key details needed to answer that question are not material to any investigation that FBI should be engaging in.

And he’s saying it just before campaign season begins again in earnest.

Obama Administration Changed the Rationale for Why Assassinations Don’t Violate the Assassination Prohibition

As a number of outlets have reported, the Second Circuit last month upheld the government’s effort to keep a March 29, 2002 OLC memo pertaining to targeted killing secret; the opinion was unsealed yesterday. The government is probably doing so to keep changes in their rationale for why assassinations don’t violate the prohibition on assassination in EO 12333 secret.

The judges on the panel — especially Judge Jon Normand, who wrote the opinion — had pushed during an ex parte hearing in June to release language in that earlier memo because the dog & pony show around drone strikes in 2012 to 2013 had used closely related language. But after some more secret briefing, the court decided the application of EO 12333 was different enough such that it remained properly protected.

It seems highly likely the specific part of EO 12333 under discussion pertains to the assassination ban. Between the earlier hearing and the opinion, the court pointed to language in the March 25, 2010 Harold Koh speech, the March 5, 2012 Eric Holder speech, and the April 30, 2012 John Brennan speech on targeted killing (they also pointed to two Panetta comments). Each of the cited speeches discusses the assassination ban — and little else that might directly pertain to EO 12333, besides just generally covert operations authorized under Article II. There’s this language in Koh’s speech.

Fourth and finally, some have argued that our targeting practices violate domestic law, in particular, the long-standing domestic ban on assassinations. But under domestic law, the use of lawful weapons systems—consistent with the applicable laws of war—for precision targeting of specific high-level belligerent leaders when acting in self-defense or during an armed conflict is not unlawful, and hence does not constitute “assassination.”

This language in Holder’s speech,

Some have called such operations “assassinations.” They are not, and the use of that loaded term is misplaced. Assassinations are unlawful killings. Here, for the reasons I have given, the U.S. government’s use of lethal force in self defense against a leader of al Qaeda or an associated force who presents an imminent threat of violent attack would not be unlawful — and therefore would not violate the Executive Order banning assassination or criminal statutes.

And this language in Brennan’s speech.

In this armed conflict, individuals who are part of al-Qa’ida or its associated forces are legitimate military targets.  We have the authority to target them with lethal force just as we targeted enemy leaders in past conflicts, such as German and Japanese commanders during World War II.

But even though all these public speeches commented on this interpretation of the assassination ban, the 2nd Circuit still permitted the government to shield the earlier memo.

The transcript of the June ex parte hearing reveals one explanation for that: the earlier memo was a “far broader interpretation” of the issue.

Screen Shot 2015-11-24 at 1.51.21 PM

That’s consistent with the government’s earlier claim (which I wrote about here).

Although the district court noted that the OLC-DOD Memorandum released by this Court contained a “brief mention” of Executive Order 12,333, the district court concluded that the analysis in the March 2002 Memorandum is significantly different from any legal analysis that this Court held has been officially disclosed and for which privilege has been waived.

In other words, while the earlier memo discusses the same aspect of EO 12333 as these public speeches (again, the assassination ban is by far the most likely thing), the earlier memo uses significantly different analysis, and so it may be hidden.

The June transcript also reveals that OLC lawyers reviewed and wrote on the 2002 memo at a later time — the implication being that someone in OLC reviewed the earlier memo in 2010 when writing the Awlaki one (and curiously, that hard copy with handwritten notes is the only one DOJ claims it can find).

Screen Shot 2015-11-24 at 4.32.17 PM

There are two things I find increasingly interesting about this earlier memo about EO 12333 — including at least one part presumably about the assassination ban. First, the implication that one of the lawyers reviewing it in 2010 saw the need to write a new memo (perhaps seeing the need to clean up yet more crazy John Yoo language? who knows). As I repeat endlessly, we know there’s a memo of uncertain date in which Yoo said the President could pixie dust the plain language of EO 12333 without changing the public language of it, and it’s possible this is what that memo did (though the President was clearly pixie dusting surveillance rules).

But I’m also interested in the date: March 29, 2002. The day after we captured Abu Zubaydah (who, at the time, top officials at least claimed to believe was a top leader of al Qaeda). The SSCI Torture Report made it clear the CIA originally intended to disappear detainees. Were they planning to execute them? If so, what stopped things?

In any case, CIA won its battle to hide this earlier discussion so we may never know. But it appears that DOJ may have felt the need to think thing through more seriously before drone assassinating a US citizen. So there is that.

 

The Source of the Section 702 Limitations: Special Needs?

Way back in 2013, in Marty Lederman’s review of the NSA Review Group’s Report, he pointed to the Report’s suggestion that Section 702 collection was limited to use with counterterrorism, counterproliferation, and cybersecurity.

The Report contains an interesting clue about how the government is presently using Section 702 that I do not recall being previously disclosed—and raises a related question about legal authorities under that provision of the FAA:

The Report explains (page 136) that in implementing Section 702, “NSA identifies specific ‘identifiers’ (for example, e-mail addresses or telephone numbers) that it reasonably believes are being used by non-United States persons located outside of the United States to communicate foreign intelligence information within the scope of the approved categories (e.g., international terrorism, nuclear proliferation, and hostile cyber activities).

[snip]

Later, on pages 152-53, the authors “emphasiz[e] that, contrary to some representations,section 702 does not authorize NSA to acquire the content of the communications of masses of ordinary people.  To the contrary, section 702 authorizes NSA to intercept communications of non-United States persons who are outside the United States only if it reasonably believes that a particular ‘identifier’ (for example, an e-mail address or a telephone number) is being used to communicate foreign intelligence information related to such matters as international terrorism, nuclear proliferation, or hostile cyber activities.”  (Italics in original.)

I may be mistaken, but I don’t believe that there’s anything in the statute itself that imposes the limitations in bold–neither that the NSA must use such “identifiers,” nor that international terrorism, nuclear proliferation, and hostile cyber activities are the only topics of acceptable foreign intelligence information that can be sought.  Perhaps the FISC Court has insisted upon such limits; but, as far as I know, the Section 702 authority as currently codified is not so circumscribed.

Of course, if you’re a regular emptywheel reader, you likely know where this has been suggested in the past, since I’ve been pointing out this apparent limitation to Section 702 since June 10 and discussed some implications of it here, here, and here.

In a response to Lederman, Julian Sanchez provided some specific cautions about treating these category limits as true “limitations.” He suggests it is unlikely that the Intelligence Community or the FISA Court would impose such limitations.

The 702 language, codified at 50 U.S.C. §1881a, permits the NSA to acquire any type of “foreign intelligence information,” which is defined extraordinarily broadly to encompass, inter alia, anything that relates to the “conduct of the foreign affairs of the United States.” But here we have the Review Group suggesting repeatedly that 702 surveillance is only for acquiring certain specific types of foreign intelligence information, related to nuclear proliferation, international terrorism, or cybersecurity. Have the intelligence agencies or the FISC imposed a more restricted reading of “foreign intelligence information” than the FISA statute does? I doubt it.

While I agree with most of Sanchez’ other cautions, I actually do think it likely that the FISC conducts a review that ends up in such limited certifications. They did it for application of Section 215 to the phone dragnet (which legally could have been used for counterintelligence purposes) and I think they may well have done so with Section 702.

FISCR only ruled bulk content collection legal for “national security” foreign intelligence purposes

We’ll learn whether I’m right or not when the FISC releases more of the 2008 Yahoo challenge to Protect America Act directives. But there is enough detail in the unclassified August 22, 2008 FISA Court of Review opinion released in early 2009 to suggest where that limitation may have come from.

The FISCR opinion, written by Bruce Selya, describes the certifications before the Court as limited to “foreign intelligence for national security purposes,” a limitation that already circumscribes PAA (and the FISA Amendments Act, as Sanchez has laid out), which allow their use for foreign intelligence generally.

In essence, as implemented, the certifications permit surveillances conducted to obtain foreign intelligence for national security purposes when those surveillances are directed against foreign powers or agents of foreign powers reasonably believed to be located outside the United States. [my emphasis]

This limitation is important because of the way Selya deals with the affirmation, in the FISC ruling before the FISCR, that there is a foreign intelligence exception to the Fourth Amendment: by instead finding a special needs exception to the Fourth tied to national security. Read more

David Kris Joins Ben Wittes in His NAKED! Choir

I know, I know. I’ve promised my substantive post on David Kris’ paper on the phone and Internet dragnets.

I know, I know. My repeated harping on the failure to inform the 2011 House freshmen about the dragnet is getting tedious.

But Kris dedicated 16 pages of his 67 page paper to arguing that the statutory requirements for briefing Congress about the dragnets (which Kris says require only Intelligence and Judiciary Committee briefing) have been met. He ultimately makes a half-hearted attempt to make the same argument Claire Eagan did about Congress adopting judicial interpretation. And he lays out the fatally weak case Ben Wittes has in the past to justify his wails of NAKED!

In doing so, Kris claims that, “all Members were offered briefings on the FISC’s interpretation.”

The briefings and other historical evidence raise the question whether Congress’s repeated reauthorization of the tangible things provision effectively incorporates the FISC’s interpretation of the law, at least as to the authorized scope of collection, such that even if it had been erroneous when first issued, it is now—by definition—correct. There is a basic principle of statutory construction that “Congress is presumed to be aware of an administrative or judicial interpretation of a statute and to adopt that interpretation when it reenacts a statute without change,”208 as it did repeatedly with the tangible things provision.

[snip]

Of course, it would be ridiculous to presume that Congress adopted a classified interpretation of a law of which it could not have been aware. As described above, however, the historical record shows that many Members were aware, and that all Members were offered briefings on the FISC’s interpretation, even if they did not attend the briefings.

And yet, in all those 16 pages, he offers not one whit of evidence that the 93 members of Congress elected in 2010 (save the 7 on the Intelligence and Judiciary Committees) could have learned about the program save two briefings offered in May 2011.

Unless you count this argument, which suffers from a basic logic problem.

In an unclassified report published in March 2011, the Senate Intelligence Committee emphasized that it had offered a briefing to all Members of Congress concerning the bulk telephony metadata collection:

Prior to the extension of the expiring FISA provisions in February 2010, the Committee acted to bring to the attention of the entire membership of the Senate important information related to the nature and significance of the FISA collection authority subject to sunset. Chairman Feinstein and Vice Chairman Bond notified their colleagues that the Attorney General and the DNI had provided a classified paper on intelligence collection made possible under the Act and that the Committee was providing a secure setting where the classified paper could be reviewed by any Senator prior to the vote on passage of what became Public Law 111–141 to extend FISA sunsets. [my bold]

The entire membership of the Senate, after all, is not the same thing as “all Members of Congress.”

Ultimately, though, Kris concedes (citing just the white paper, and not citing me, the Guardian, any other reporting, or Justin Amash’s public statements to the effect) that just maybe this information wasn’t passed on in 2011 — but don’t worry, the Executive did its job!

Although the House Intelligence Committee did notify Members of the House of the classified documents and briefings in 2010 (when it was led by Chairman Sylvestre Reyes), it may not have done so in 2011 (when it was led by Chairman Mike Rogers). See White Paper at 18 n.13.

[snip]

Regardless of any intracongressional issues in 2011, as a matter of inter-branch relations, it is clear that the Executive Branch provided the materials with the intent that they be made available to all Members of Congress, as they had been in 2009.

Now, Kris is a much better lawyer than the flunkies who wrote the Administration’s far weaker White Paper on Section 215, and his argument here betrays not only that, but, I suspect, a hint that he realizes the flaw in his argument.

Notice in his claim that “all Members were offered briefings on the FISC’s interpretation,” he doesn’t argue all members got the Executive Branch notices on the program. He doesn’t argue that all members got briefed on the content on the notices. Rather, he claims only that they were offered briefings on the FISC’s interpretation.

Read more

Scott Shane Defends the Commander-in-Chief’s Language

NYT’s excellent new ombud, Margaret Sullivan, returns to a perennial ombud issue, how the Grey Lady refers to Executive Branch actions and abuses. She includes a long quote from Scott Shane that reveals a great deal about his reporting, and ultimately convinces me we should be calling drone killing assassination.

Adherence to “Targeted Killing” Even While Admitting It’s Not

Let’s start with Shane’s defense of the term “targeted killing” (a term I sometimes use but should not). Sadly, Sullivan cuts off the direct quote from Scott Shane at its most important part, but in the following, the first paragraph here is a direct quote from Shane, the second Sullivan’s report of his comment.

This leaves “targeted killing,” which I think is far from a euphemism. It denotes exactly what’s happening: American drone operators aim at people on the ground and fire missiles at them. I think it’s a pretty good term for what’s happening, if a bit clinical.

Mr. Shane added that he had only one serious qualm about the term. That, he said, was expressed by an administration official: “It’s not the targeted killings I object to — it’s the untargeted killings.” The official “was talking about so-called ‘signature strikes’ that target suspected militants based on their appearance, location, weapons and so on, not their identities, which are unknown; and also about mistaken strikes that kill civilians.”

Shane defends using “targeted killing,” even while admitting that a great deal of drone killing is not targeted. Unless Shane knows a great deal more about individual strikes than he lets on — and therefore knows which drone strikes are targeted at known identities and which are targeted at crowds of unknown military aged males — then he is party to an apparently deliberate strategy on the part of the Administration to spin its killing program as much more orderly and legally justified than it actually is. We saw this operate as recently as yesterday, when John Brennan responded to a question from Jan Schakowsky about signature strikes by telling her to look back at speeches that address only “targeted killing.”

SCHAKOWSKY: Let me ask you this, is there any way that you can define and distinguish between targeted strikes and signature strikes by the — by drones?

BRENNAN: I would refer to the comments that were made by a number of U.S. government officials publicly in speeches, including when I was at the White House. I’m not going to engage in any type of discussion on that here to the Congress, ma’am.

As I said, I’m as guilty of using this term without sufficient awareness as Shane. But doing so consciously really is participating in a propaganda effort the Administration is engaged in.

Executive Order 12333’s Invisible Ink

Then there’s Shane’s refusal to use “assassination” based on Administration claims about Executive Order 12333, which ostensibly prohibits the practice.

“Assassination” is banned by executive order, but for decades that has been interpreted by successive administrations as prohibiting the killing of political figures, not suspected terrorists. Read more

The NYT Grants David Barron and Marty Lederman a Mulligan on 18 USC 1119

I’ll have far more to say about this irresponsibly credulous accounting of the background to the Anwar al-Awlaki killing from the NYT tomorrow. But for the moment I wanted to point to an interesting detail about the genesis of the June-July 2010 OLC memo.

The NYT explains that David Barron and Marty Lederman wrote an initial short OLC memo to authorize Anwar al-Awlaki’s killing. But then, after reading a blog post that describes why such a killing would be a violation of 18 USC 1119, they decided they needed to do a more thorough memo.

According to officials familiar with the deliberations, the lawyers threw themselves into the project and swiftly completed a short memorandum. It preliminarily concluded, based on the evidence available at the time, that Mr. Awlaki was a lawful target because he was participating in the war with Al Qaeda and also because he was a specific threat to the country. The overlapping reasoning justified a strike either by the Pentagon, which generally operated within the Congressional authorization to use military force against Al Qaeda, or by the C.I.A., a civilian agency which generally operated within a “national self-defense” framework deriving from a president’s security powers.

They also analyzed other bodies of law to see whether they would render a strike impermissible, concluding that they did not. For example, the Yemeni government had granted permission for airstrikes on its soil as long as the United States did not acknowledge its role, so such strikes would not violate Yemeni sovereignty.

And while the Constitution generally requires judicial process before the government may kill an American, the Supreme Court has held that in some contexts — like when the police, in order to protect innocent bystanders, ram a car to stop a high-speed chase — no prior permission from a judge is necessary; the lawyers concluded that the wartime threat posed by Mr. Awlaki qualified as such a context, and so his constitutional rights did not bar the government from killing him without a trial.

But as months passed, Mr. Barron and Mr. Lederman grew uneasy. They told colleagues there were issues they had not adequately addressed, particularly after reading a legal blog that focused on a statute that bars Americans from killing other Americans overseas. In light of the gravity of the question and with more time, they began drafting a second, more comprehensive memo, expanding and refining their legal analysis and, in an unusual step, researching and citing dense thickets of intelligence reports supporting the premise that Mr. Awlaki was plotting attacks. [my emphasis]

This post — an April 8, 2010 post entitled “Let’s Call Killing al-Awlaki What It Is — Murder” — is almost certainly the blog post in question. There’s almost nothing else written on 1119 (there’s this legal journal article, but from Fall 2011), much less focusing specifically on Awlaki and published in a legal blog.

Which is interesting, because the post describes one of the possible bases for arguing that 1119 does not apply to the killing of Awlaki that Obama is just ignoring the statute as Commander-in-Chief.

Which leads us to the second possible explanation of why 18 USC 1119 does not apply: because Obama has authorized the CIA to kill al-Awlaki.  That explanation seems implicit in much of the media’s coverage of the Obama administration’s decision; I have yet to see any reporter ask why Obama believes he has the legal authority to order Americans killed, given that 18 USC 1119 specifically criminalizes such killings.  The argument, however, is deeply problematic — and eerily reminiscent of debates over the Bush administration’s authorization of torture. The Bush administration argued that Bush had the authority as Commander-in-Chief to ignore the federal torture statute, 18 USC 2340; the Obama administration seems to now be arguing, albeit implicitly, that Obama has the authority as Commander-in-Chief to ignore the foreign-murder statute.

As I noted, while the white paper, at least, plays a neat rhetorical game to collapse AUMF and Article II authorizations, ultimately it uses this language to explain why an Article II authorized killing of Awlaki would not violate 1119.

Similarly, under the Constitution and the inherent right to national self-defense recognized in international law, the President may authorize the use of force against a U.S. citizen who is a member of al-Qa’ida or its associated forces who poses an imminent threat of violent attack against the United States.

In other words, the white paper, at least, does precisely what Kevin Jon Heller warned might be so troubling — it said that if the President authorized Awlaki’s killing, it would mean 1119 would not apply.

To the extent that the white paper fairly reflects the content of the OLC memo, then, David Barron and Marty Lederman failed to find a counterargument to precisely the argument that appears to have convinced them to write a second, longer OLC memo in the first place.

Which may be why the NYT article goes to such lengths to try to explain away this apparent problem.

Read more

Targeted Killing Timeline

A timeline!

I’ve been working on this timeline for almost nine months, trying to pull together the known dates about strikes against Americans, the evidence supporting the strike against Anwar al-Awlaki, the legal cases surrounding both targeted killing and torture, to which targeted killing is linked via the Memorandum of Notification, and Congressional efforts to exercise oversight.

September 17, 2001: George Bush signs Memorandum of Notification (henceforth, Gloves Come Off MON) authorizing a range of counterterrorism techniques, including torture and targeted killing.

September 18, 2001: Congress passes the Authorization to Use Military Force.

November 3, 2002: US citizen Kamal Derwish killed in drone purportedly targeting Abu Ali al-Harithi.

Late 2008: Ruben Shumpert reported killed in Somalia.

June 24, 2009: Leon Panetta gets briefed on assassination squad program.

June 26, 2009: HPSCI passes a funding authorization report expanding the Gang of Eight briefings.

July 8, 2009: The Administration responds with an insulting appeal to a “fundamental compact” between Congress and the President on intelligence matters.

July 8, 2009: Silvestre Reyes announces CIA lied to Congress.

October 26, 2009: British High Court first orders British government to release language on Binyam Mohamed’s treatment.

October 28, 2009: FBI kills Imam Luqman Asmeen Abdullah during Dearborn, MI arrest raid.

October 29, 2009: Hearing on declassifying mention of Gloves Come Off MON before Judge Alvin Hellerstein; in it, Hellerstein reveals NSA James Jones has submitted declaration to keep mention of MON secret.

November 5, 2009: Nidal Hasan attacks Fort Hood, killing 13.

December 24, 2009: JSOC tries but fails to hit Anwar al-Awlaki. On that day, the IC did not yet believe him to be operational.

December 25, 2009: With Umar Farouk Abdulmutallab attack, FBI develops full understanding of Awlaki’s operational goals.

January 2, 2010: In conversation with David Petraeus, Yemeni President Ali Abdullah Saleh http://www.cablegatesearch.net/cable.php?id=10SANAA4“>speaks as if Awlaki, whom he refers to as a cleric, not an AQAP member, was a designated target of December 24 attack.

Read more

Is One of the Anwar al-Awlaki Memos a Revised Imminence Standard?

I’ve been working on a theory on why the white paper is so crappy based, in part, on a problem international law experts keep making. For my purposes, Noura Erakat’s description of the problem will suffice, but a ton of people have raised it.

Imminence is one element of the law of self defense and has no bearing upon the lawfulness of a target where there is an existing armed conflict. Instead, in ongoing hostilities, the legality of a target is a status-based assessment that distinguishes combatants from civilians. Unless he surrenders, a combatant can be killed regardless of activity. In contrast, a civilian retains his immunity unless he directly participates in hostilities, which is subject to a wholly distinct legal analysis. The point is this: if Al-Awlaki, or another target, is indeed a combatant in the U.S.’s ongoing hostilities authorized by the 2001 Authorization for the Use of Military Force (AUMF), an imminence analysis is not relevant at all.

If, as the white paper sort of suggests, the AUMF is what justifies Anwar al-Awlaki’s killing and the government had evidence he was operational (that is, a legitimate combatant with AQAP after the point when AQAP was added to the official AQ roster) then imminence should be moot. So why is it in there, particularly in such a crazyass form?

Consider, though, that we know there are multiple memos: two, according to DiFi, in the opening moments of the John Brennan hearing, though Ron Wyden insisted the Committee hadn’t received all the targeted killing memos and DiFi may have said they’re waiting on 8 more.

Also we know that Ron Wyden has been asking whether the Administration killed Awlaki under AUMF or Article II authorities, suggesting that the Administration may be making arguments based on one or another in different memos.

So I’m going to advance the wildarsed guess that — rather than being a simple summary of the June 2010 memo we know about — the white paper is actually a pained amalgam meant to encompass the more radical memos, while still retaining some patina of whatever decent argument Marty Lederman and David Barron made in June 2010.

Read more

Why the Iraq AUMF Still Matters

The big headline that came out of yesterday’s American Bar Association National Security panels is that DOD General Counsel Jeh Johnson and CIA General Counsel Stephen Preston warned that US citizens could be targeted as military targets if the Executive Branch deemed them to be enemies.

U.S. citizens are legitimate military targets when they take up arms with al-Qaida, top national security lawyers in the Obama administration said Thursday.

[snip]

Johnson said only the executive branch, not the courts, is equipped to make military battlefield targeting decisions about who qualifies as an enemy.

We knew that. Still, it’s useful to have the Constitutional Lawyer President’s top aides reconfirm that’s how they function.

But I want to point to a few other data points from yesterday’s panels (thanks to Daphne Eviatar for her great live-tweeting).

First, Johnson also said (in the context of discussions on cyberspace, I think),

Jeh Johnson: interrupting the enemy’s ability to communicate is a traditionally military activity.

Sure, it is not news that the government (or its British allies) have hacked terrorist “communications,” as when they replaced the AQAP propaganda website, “Insight,” with a cupcake recipe (never mind whether it’s effective to delay the publication of something like this for just one week).

But note what formula Johnson is using: they’ve justified blocking speech by calling it the communication of the enemy. And then apparently using Jack Goldsmith’s formulation, they have said the AUMF gives them war powers that trump existing domestic law, interrupting enemy communications is a traditional war power, and therefore the government can block the communications of anyone under one of our active AUMFs.

Johnson also scoffed at the distinction between the battlefield and the non-battlefield.

Jeh Johnson: the limits of “battlefield v. Non battlefield is a distinction that is growing stale.” But then, it’s not a global war. ?

Again, this kind of argument gets used in OLC opinions to authorize the government targeting “enemies” in our own country. On the question of “interrupting enemy communication,” for example, it would seem to rationalize shutting down US based servers.

Then, later in the day Marty Lederman (who of course has written OLC opinions broadly interpreting AUMF authorities based on the earlier Jack Goldsmith ones) acknowledged that Americans aren’t even allowed to know everyone the US considers an enemy.

Lederman: b/c of classification, “we’re in armed conflicts with some groups the American public doesn’t know we’re in armed conflict with.”

Now, as I’ve noted, one of the innovations with the Defense Authorization passed yesterday is a requirement that the Executive Branch actually brief Congress on who we’re at war with, which I take to suggest that Congress doesn’t yet necessarily know everyone who we’re in “armed conflict” with.

Which brings us to how Jack Goldsmith defined the “terrorists” whom the government could wiretap without a warrant.

the authority to intercept the content of international communications “for which, based on the factual and practical considerations of everyday life on which reasonable and prudent persons act, there are reasonable grounds to believe … [that] a party to such communication is a group engaged in international terrorism, or activities in preparation therefor, or any agent of such a group,” as long as that group is al Qaeda, an affiliate of al Qaeda or another international terrorist group that the President has determined both (a) is in armed conflict with the United States and (b) poses a threat of hostile actions within the United States;

It’s possible the definition of our enemy has expanded still further since the time Goldsmith wrote this in 2004. Note Mark Udall’s ominous invocation of “Any other statutory or constitutional authority for use of military force” that the Administration might use to authorize detaining someone. But we know that, at a minimum, the Executive Branch used the invocations of terrorists in the Iraq AUMF–which are much more generalized than the already vague definition of terrorist in the 9/11 AUMF–to say the President could use war powers against people he calls terrorists who have nothing to do with 9/11 or al Qaeda.

So consider what this legal house of cards is built on. Largely because the Bush Administration sent Ibn Sheikh al-Libi to our Egyptian allies to torture, it got to include terrorism language in an AUMF against a country that had no tie to terrorism. It then used that language on terrorism to justify ignoring domestic laws like FISA. Given Lederman’s language, we can assume the Administration is still using the Iraq AUMF in the same way Goldsmith did. And yet, in spite of the fact that the war is ending, we refuse to repeal the AUMF used to authorize this big power grab.