与「sole」相关的搜索结果

𝗧𝗛𝗜𝗦 𝗜𝗦 𝗠𝗨𝗖𝗛 𝗕𝗜𝗚𝗚𝗘𝗥 𝗧𝗛𝗔𝗡 “𝗧𝗛𝗘 𝗣𝗘𝗡𝗧𝗔𝗚𝗢𝗡 𝗠𝗔𝗬 𝗨𝗦𝗘 𝗔𝗜.” President Donald Trump’s new Executive Order signals a fundamental change in defense acquisition: contractors will increasingly be expected to prove where critical materials, components, equipment, and software originate—through subcontractors and toward the raw-material source. The Pentagon wants to see the defense supply chain, identify where an adversary could interrupt it, and make prohibited foreign sourcing harder to excuse. The order directs the Department of Defense to: • Map designated critical supply chains. • Obtain hierarchical bills of materials showing what is inside a defense product, who supplied it, and where it originated. • Extend visibility beyond prime contractors into lower-tier suppliers. • Identify foreign dependencies, bottlenecks, sole-source suppliers, concentration risks, and single points of failure. • Use AI to analyze acquisition data and expose connections conventional contract reviews may miss. • Accelerate qualification of alternative sources and materials. Beginning January 1, 2027, certain waivers involving covered materials from prohibited sources will become substantially harder to obtain. Contractors seeking waivers may need approved mitigation plans showing how the dependency will be reduced or removed. Fraud, deliberate misrepresentation, or willful failure to implement an approved plan could result in contractual remedies and possible referral to the Attorney General. Restrictions under 10 U.S.C. §4872 concern designated sensitive materials from China, Russia, North Korea, and Iran, including certain specialty metals, rare-earth elements, permanent magnets, and tungsten-related materials. But one distinction matters: 𝗔𝗜 𝗜𝗦 𝗡𝗢𝗧 𝗕𝗘𝗜𝗡𝗚 𝗔𝗨𝗧𝗛𝗢𝗥𝗜𝗭𝗘𝗗 𝗧𝗢 𝗗𝗘𝗖𝗜𝗗𝗘 𝗜𝗡𝗗𝗘𝗣𝗘𝗡𝗗𝗘𝗡𝗧𝗟𝗬 𝗪𝗛𝗜𝗖𝗛 𝗖𝗢𝗠𝗣𝗔𝗡𝗜𝗘𝗦 𝗔𝗥𝗘 𝗧𝗥𝗨𝗦𝗧𝗪𝗢𝗥𝗧𝗛𝗬. AI will help map and analyze supply-chain vulnerabilities. Human officials retain responsibility for waivers, mitigation plans, contracting actions, and enforcement. President Trump and Secretary of Defense Pete Hegseth deserve recognition for this determination to expose hidden dependencies and strengthen the industrial foundation behind the American warfighter. Now comes the decisive test: implementation. AI cannot map what contractors cannot identify, subcontractors will not disclose, or suppliers report inaccurately. 𝗦𝗨𝗣𝗣𝗟𝗬-𝗖𝗛𝗔𝗜𝗡 𝗠𝗔𝗣𝗣𝗜𝗡𝗚 𝗜𝗦 𝗡𝗢𝗧 𝗔𝗗𝗠𝗜𝗡𝗜𝗦𝗧𝗥𝗔𝗧𝗜𝗩𝗘 𝗖𝗢𝗠𝗣𝗟𝗜𝗔𝗡𝗖𝗘. 𝗜𝗧 𝗜𝗦 𝗔 𝗧𝗘𝗦𝗧 𝗢𝗙 𝗪𝗛𝗘𝗧𝗛𝗘𝗥 𝗧𝗛𝗘 𝗦𝗬𝗦𝗧𝗘𝗠 𝗕𝗘𝗛𝗜𝗡𝗗 𝗧𝗛𝗘 𝗪𝗔𝗥𝗙𝗜𝗚𝗛𝗧𝗘𝗥 𝗖𝗔𝗡 𝗦𝗨𝗥𝗩𝗜𝗩𝗘 𝗖𝗢𝗡𝗧𝗔𝗖𝗧 𝗪𝗜𝗧𝗛 𝗪𝗔𝗥. “Don’t sell me hype and call it readiness. Prove it before you put a soldier’s life behind it.” — Linda Restrepo Editor-in-Chief, N360™ — Sovereign Intelligence & National Security Technologies #DefenseSupplyChain# #ArtificialIntelligence# #DefenseIndustrialBase# #NationalSecurity# #MilitaryReadiness#

Democratic lawmakers accused the Trump administration of abusing its power after officials admitted in a federal court filing they recommended terminating several billion dollars in grants for clean-energy projects based “solely” on states’ “political identity” and whether President Donald Trump won the vote there in the 2024 election.

An LLM's job is reasoning, not security. Relying solely on built-in model guardrails leaves you open to advanced attacks. See why you need a dedicated safety layer like Model Armor between your users and your agents →

"We love you. We love your child." President Trump shares a preview of the heartfelt message he plans to deliver during the dignified transfer of four U.S. service members killed in the war with Iran. "They're their children. There's no games, no nothing. That's their child," Trump says. "All you can do is throw out your heart." Trump is expected to attend the solemn ceremony at Dover Air Force Base as the remains of the four fallen service members are returned home and their families are honored.

Nonce-Generation Vulnerability in the Zilliqa Ledger App: A critical vulnerability has been identified in the Zilliqa Ledger application affecting the generation of Schnorr signatures for native (non-EVM) Zilliqa transactions. The vulnerability causes signatures to be generated with a predictably weakened ephemeral nonces, from which an attacker can recover the signer’s private key using only publicly available on-chain data. Protective measures are already in place to prevent further loss, and a coordinated remediation plan is being finalised. Users who have signed native Zilliqa transactions with a Ledger device should await official guidance before taking any action. Impact: The vulnerability affects private keys used to sign native Zilliqa transactions with a Ledger device. Any account that has broadcast approximately five or more native transactions signed through the Zilliqa Ledger app should be considered compromised. Its private key can be reconstructed from signatures already recorded on-chain, regardless of any subsequent software update. The issue is confined to the Ledger app’s native signing path. EVM transactions are unaffected. Zilliqa software development kits, including zilliqa-js, gozilliqa-sdk and pyzil, generate nonces correctly and are not affected. Root cause: Zilliqa native transactions are authenticated using EC-Schnorr signatures over secp256k1. Each signature requires a fresh, uniformly random 256-bit ephemeral nonce, (k). The secrecy and full-width randomness of (k) are essential, as any systematic bias can allow the private key to be recovered. The signing routine generated 40 bytes of randomness and reduced them modulo the curve order, correctly producing a uniform 256-bit value. However, when copying this value into the nonce buffer, the code copied the wrong 32 bytes of the 40-byte output. This retained the eight zero-padding bytes introduced by the reduction and discarded eight bytes of entropy. As a result, the most significant 64 bits of every generated nonce were fixed at zero, meaning (k < 2^{192}). A nonce with 64 known bits leaks information about the private key with each signature. With five or more affected signatures, the private key can be recovered in seconds using commodity hardware by solving the resulting Hidden Number Problem through lattice reduction - a well-documented technique for attacking biased-nonce signatures. Because the affected transactions are permanently recorded on-chain, this exposure cannot be reversed by updating the signing application. The affected keys must be retired. Timeline 2019-2026: The defect was present in every released version of the Zilliqa Ledger app across all supported devices. 19 July 2026: On-chain activity consistent with active exploitation was observed. 21 July 2026: The root cause was isolated to the app’s nonce-handling code and confirmed by reproducing the issue against on-chain signatures. Ongoing: A corrected version of the app is being prepared in coordination with Ledger. Release details will be announced separately. Remediation: As soon as the issue was identified, native (non-EVM) transactions were suspended as a protective measure. This has halted further draining of affected accounts while a solution is prepared. Affected accounts cannot be secured through an ordinary transfer. Because their private keys can be derived from data already recorded on-chain, an attacker with access to the same key could attempt to front-run a legitimate transfer as soon as transactions resume. Advising users simply to move their funds would therefore be ineffective and potentially unsafe. A corrected build of the Ledger app has been prepared, restoring full-width nonce generation and preventing further weakened signatures from being produced. However, this does not protect keys that have already been used to sign affected transactions. Those keys must ultimately be retired. A coordinated remediation plan to secure affected balances is being finalised and will be published separately. Until then, users who have signed native Zilliqa transactions with a Ledger device should take no independent action and should rely solely on official Zilliqa channels for instructions. Users who hold or transact with ZIL exclusively through EVM-compatible tooling are not affected. Acknowledgments: @kucoincom played a key role in pinpointing the root cause in the Zilliqa Ledger app nonce generation, recovered affected private keys from publicly available on-chain signatures, and confirmed ongoing exploitation. KuCoin’s timely reporting and responsible collaboration enabled rapid protective measures, helping safeguard users, ecosystem participants, and the broader Zilliqa ecosystem while the remediation plan was being developed. We sincerely appreciate the KuCoin team’s professionalism, technical expertise, and cooperation throughout this process.

You may never meet your idols—but you can always wear their sneakers. 🐍👟 Anna Bediones shares why the Nike Kobe 6 holds a special place in her collection. Catch EVERY SOLE STORIES EPISODE ON YOUTUBE: