AG Jeff Sessions Met with Russian Ambassador Twice in 2016, Something He Lied About

AG Jeff Sessions Met with Russian Ambassador Twice in 2016, Something He Lied About

In a bombshell piece The Washington Post has reported that Attorney General Jeff Sessions twice met with Russia’s ambassador to the U.S. last year, something he lied about during his confirmation hearing.

(Photo: AP)

According to the Post, Sessions had a private phone conversation with Russian Ambassador Sergey Kislyak that took place in September in Session’s office. The call was made “at the height of what U.S. intelligence officials say was a Russian cyber campaign to upend the U.S. presidential race.”

At the time of the conversation Sessions was not only a senior member of the Armed Services Committee; he was one of then-candidate Trump’s top foreign policy advisers.

During Session’s confirmation hearing in the Judiciary Committee on January 10th, Sen. Al Franken (D-Minn.) asked him what actions he would take if he was presented evidence that someone affiliated with the Trump campaign communicated with the Russian government in the course of the 2016 campaign.

“I’m not aware of any of those activities,” said Sessions. “I have been called a surrogate at a time or two in that campaign and I did not have communications with the Russians.”

Recently President Trump fired Michael Flynn, his pick for National Security Advisor, over his failure to properly disclose contacts with Russia. This precedent could very well lead to Trump also firing Sessions, something cannabis advocates would clearly applaud given his recent and past derogatory statements regarding the plant and laws that legalize it.

About Anthony Martinelli

Anthony, co-founder and Editor-in-Chief of TheJointBlog, has worked closely with numerous elected officials who support cannabis law reform, including as the former Campaign Manager for Washington State Representative Dave Upthegrove. He has also been published by multiple media outlets, including the Seattle Times. He can be reached at TheJointBlog@TheJointBlog.com.

(Why?)

Published at Thu, 02 Mar 2017 03:45:16 +0000