Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Jonathan Wakely
Congress Passes Bill Prohibiting Sharing or Selling Americans’ Sensitive Data to Entities Controlled by Foreign Adversaries
On April 24, 2024, President Biden signed into law H.R. 815, which includes the Protecting Americans’ Data from Foreign Adversaries Act of 2024 (“the Act”), a bill that passed the House 414-0 as H.R. 7520 on March 20. The Act is one of several recent actions by the U.S. government to regulate transfers of U.S. personal data for national security reasons, with a particular focus on China.
CFIUS Transaction Approvals Taking Longer
CFIUS Transaction Approvals Taking Longer The Committee on Foreign Investment in the United States, or CFIUS, recently released the public version of its annual report to Congress regarding its review of certain transactions involving foreign investment during 2022.
Comments Due August 31 on FCC’s Proposal to Step Up Review of Foreign Ownership in Telecom Carriers and Establish Cybersecurity Requirements
Jonathan Wakely practices at the intersection of national security and the private sector, advising clients on a range of significant international trade, cross-border investment, national security, supply chain security, and public policy matters.
Comments Due August 31 on FCC’s Proposal to Step Up Review of Foreign Ownership in Telecom Carriers and Establish Cybersecurity Requirements
Last week, comment deadlines were announced for a Federal Communications Commission (“FCC”) Order and Notice of Proposed Rulemaking (“NPRM”) that could have significant compliance implications for all holders of international Section 214 authority (i.e., authorization to provide telecommunications services from points in the U.S. to points abroad).
Comments Due August 31 on FCC’s Proposal to Step Up Review of Foreign Ownership in Telecom Carriers and Establish Cybersecurity Requirements
Jonathan Wakely practices at the intersection of national security and the private sector, advising clients on a range of significant international trade, cross-border investment, national security, supply chain security, and public policy matters. Mr. Wakely has been recognized by Chambers USA for his leading expertise in securing national security-related regulatory approvals for foreign investments.
CFIUS Issues Guidance On Disclosure of Information About Limited Partner Investors and Application of Mandatory Filing Rules to Multi-stage Transactions
May 23, 2023, Covington Alert The U.S. Department of the Treasury (“Treasury”), in its capacity as chair of the Committee on Foreign Investment in the United States (“CFIUS” or the “Committee”), recently posted two new frequently asked questions (“FAQs”) to CFIUS’s website that have important implications for parties planning transactions subject to the Committee’s jurisdiction.
CFIUS Issues Guidance On Disclosure of Information About Limited Partner Investors and Application of Mandatory Filing Rules to Multi-stage Transactions
The U.S. Department of the Treasury (“Treasury”), in its capacity as chair of the Committee on Foreign Investment in the United States (“CFIUS” or the “Committee”), recently posted two new frequently asked questions (“FAQs”) to CFIUS’s website that have important implications for parties planning transactions subject to the Committee’s jurisdiction.
FCC Steps Up Review of Foreign Ownership in Telecom Carriers; Proposes Cybersecurity Mandates
Jonathan Wakely practices at the intersection of national security and the private sector, advising clients on a range of significant international trade, cross-border investment, national security, supply chain security, and public policy matters.
National Security Update - Departments of Commerce and Treasury Release Notice of Proposed Rulemaking Regarding CHIPS “Guardrails”
Jonathan Wakely practices at the intersection of national security and the private sector, advising clients on a range of significant international trade, cross-border investment, national security, supply chain security, and public policy matters. Mr. Wakely has been recognized by Chambers USA for his leading expertise in securing national security-related regulatory approvals for foreign investments.
National Security Update - Departments of Commerce and Treasury Release Notice of Proposed Rulemaking Regarding CHIPS “Guardrails”
On March 21, 2023, the Department of Commerce (“Commerce”) published a Notice of Proposed Rulemaking (the “Commerce Proposed Rule”) to implement certain provisions of the CHIPS and Science Act of 2022 (“CHIPS Act”) that place restrictions on certain activities of businesses receiving federal funding pursuant to the CHIPS Act (“Commerce Guardrails”).
Will 2023 Be an Inflection Point for CFIUS?
Will 2023 Be an Inflection Point for CFIUS? On the heels of Russia’s invasion of Ukraine, pandemic-induced supply chain disruptions and U.S.-China tensions over Taiwan, 2022 accelerated a sweeping effort within the U.S. government to make national security considerations — especially with respect to China — a key feature of new and existing regulatory processes.
Frequently Asked Questions and Answers Regarding the Trump Administration’s Push to Secure Supply Chains in the United States/New Interagency Effort Aimed at Expanding Sectors, Measures | LexBlog
It has been publicly reported that discussions are underway within the Trump Administration for a coordinated interagency initiative to remove key industrial supply chain dependencies from overseas, especially China, and redouble efforts to secure such supply chains in the United States.
Why does git status show branch is up-to-date when changes exist upstream?
What the status is telling you is that you're behind the ref called origin/master which is a local ref in your local repo. In this case that ref happens to track a branch in some remote, called origin, but the status is not telling you anything about the branch on the remote. It's telling you about the ref, which is just a commit ID stored on your local filesystem (in this case, it's typically in a file called .git/refs/remotes/origin/master in your local repo).
If clang++ and g++ are ABI incompatible, what is used for shared libraries in binary?
clang++ and g++ are ABI incompatible, even for things as core as standard containers, according to, i.e. the clang++ website. Debian ships with C++ shared libraries, i.e. libboost, etc... that are compiled with ~something and user programs using both compiler generally work, and the library names aren't mangled with the compiler that was used for them. When you install clang, debian doesn't go and pull in duplicate versions of every C++ library installed on your system. What's the deal?
Why is there no safe alternative to unique_ptr::operator*()?
std::vector has the member function at() as a safe alternative to operator[], so that bound checking is applied and no dangling references are created: void foo(std::vector<int> const&x) { const auto&a=x[0]; // what if x.empty()? undefined behaviour! const auto&a=x.at(0); // throws exception of x.empty() } However, std::unique_ptr lacks the corresponding functionality: void foo(const std::unique_ptr<int> x) { const auto&a=*x; // what if bool(x)==false?
Re: Alleged libstdc++ vulnerabilities
From: Jonathan Wakely Date: Fri, 14 Aug 2015 18:55:01 +0100 Does anybody know what this is about and can point to the relevant PRs? “discovered serious security bugs in […] libstdc++” The USENIX paper does not back up this claim. The paper abstract says "discovered 11 previously unknown security vulnera- bilities: nine in GNU libstdc++ and two in Firefox, all of which have been confirmed and subsequently fixed by vendors.
Re: Alleged libstdc++ vulnerabilities
On 14 August 2015 at 18:49, Florian Weimer wrote: Does anybody know what this is about and can point to the relevant PRs? "discovered serious security bugs in [...] libstdc++" The USENIX paper does not back up this claim.
Non-static member initialization of char array with brace gives an error in gcc while not in clang
Consider following code: #include <iostream> class A { char name[40] = { "Blank" }; // note the braces here public: const char *getName() { return name; } }; int main() { A a; std::cout << a.getName() << std::endl; } It gives an error in gcc (latest version 5.2.0): prog.cpp:5:28: error: invalid conversion from 'const char*' to 'char' [-fpermissive] char name[40] = { "Blank" }; ^ But it's not the case for clang, that compiles it flawlessly with -std=c++11 -pedantic -Wall.
i = i++; is undefined. Is i = foo(i++) also undefined?
What would the current ISO C++ standard specify for this case? Except where noted, evaluations of operands of individual operators and of subexpressions of individual expressions are unsequenced. If a side effect on a scalar object is unsequenced relative to either another side effect on the same scalar object or a value computation using the value of the same scalar object, and they are not potentially concurrent (1.10), the behavior is undefined.
What are the problems of a zero-terminated string that length-prefixed strings overcome?
One problem is that with zero-terminated strings you have to keep finding the end of the string repeatedly. The classic example where this is inefficient is concatenating into a buffer: On every call to the program has to start from the beginning of the string and find the terminator to know where to start appending. This means the function spends more and more time finding the place to append as the string grows longer.
What is the return type of a lambda expression if an item of a vector is returned?
You should be asking what is the return type of a lambda expression if it is not specified explicitly?. The answer is given in C++11 5.1.2 [expr.prim.lambda] paragraph 5, where it says if the lambda has no statement it returns , otherwise: lvalue-to-rvalue conversion means that if the return statement returns an lvalue like it decays to an rvalue, i.e. it returns just by value.
Type trait to check that all types in a parameter pack are copy constructible
I need a type trait to check whether all types in a parameter pack are copy constructible. This is what I've done so far. The main function contains some test cases, to check the functionality. My idea was to check recursively, whether the head element of the pack is copy-constructible or not and go on further, with the tail. Unfortunately, I do not get this idea to compile. My knowledge about variadic templates is not very advanced.
Is everything in C++11 STL user-implementable?
I'm assuming you mean the C++11 standard library, not the STL (which is a library of algorithms, iterators and containers from the 1990s). The answer depends what you mean by "implemented manually". Do you mean in pure C++? i.e. no assembly code and no OS-specific features such as POSIX memory allocation functions, or even lower-level system calls to the kernel?
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Jonathan
Contact Jonathan, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack