Post Syndicated from Ryan Smith original https://www.servethehome.com/amd-ces-2026-keynote-live-coverage/
We’re down to our third and final chipmaker keynote of the day. Closing out a busy day for press conferences is AMD, who this year gets the honor of holding CES’s official opening keynote. The subject of AMD’s keynote, like so many others this year, will be a broad focus on AI, with CEO Dr. […]
The post AMD CES 2026 Keynote Live Coverage appeared first on ServeTheHome.
Post Syndicated from Grab Tech original https://engineering.grab.com/kinabalu-ai-sre
If you’ve ever been on-call during an outage, you know the drill: a flood of alerts, five dashboards open, logs streaming from different places, a dozen threads in Slack, and still no clear picture. Context-switching kills velocity, and “where do I even start?” becomes the default question.
Kinabalu AI Site Reliability Engineering (AI SRE for short) is our attempt to transform this experience. It consolidates the right context in one place, analyzes it with assistive AI agents, and helps us move from alert to action quickly.
Target audience:
Incidents today suffer from several issues, including alert overload, fragmented context across tools, slow RCA, operational redundancy from tool-hopping, and scattered runbooks that are hard to find and apply under pressure.
AI SRE solves these issues by serving a unified view that streamlines diagnostics and correlates signals to recommend the best next actions. This approach accelerates response time, further reducing time-to-resolution (TTR), lowers the cognitive load on on-calls by keeping all relevant context in one place, and strengthens collaboration through evidence-backed updates and clear ownership.
Kinabalu’s AI SRE is a 24/7 automator reachable via Slack and a Web UI. It takes input in the form of an automated alert or a direct question and responds with an evidence-backed, actionable insight.
In a hypothetical user journey with AI SRE, the process might begin with a trigger. For instance, if a monitoring alert is triggered by a fivefold increase in a Datadog report and increasing latency for a service, AI SRE initiates an incident thread and gathers the initial context.
The following components of AI SRE are then executed in sequence:
Component 1: Auto-triage with context from incident records, tagging on severity, priority, owner/oncall, as well as issue types.
Component 2: AI SRE (static diagnostics) establishes correlations by
Delivers an incident summary with actionable insights, aRCA draft, and concrete recommendations (queries to run, rollback/feature-flag options, runbook links).
Component 3: Dynamic conversation.
Under the hood, the backend combines a central signal aggregator with Model Context Protocol (MCP) servers for instant search, and a Large Language Model (LLM) powered intelligence layer that analyzes signals to auto-triage incidents and produce actionable insights.
We follow a Retrieval Augmented Generation (RAG) approach and are building a knowledge graph that stitches together incident signals across the stack. The aggregator ingests the information as follows:
With this context, AI SRE agents can provide a clear view of what changed, when it changed, and who owns it, making incident understanding and debugging faster and more reliable in a near-real-time manner.
Agents can basically “normalize” the alerts and signals, meaning they standardize and interpret them for better understanding. They can semantically search through historical changes that can explain current symptoms, correlate co-occurring signals, and surface likely causes.
AI SRE uses the SuperAgent and A2A multi-agent frameworks to analyze incidents using two workflows, which can coexist.
The static diagnostics workflow starts with a trigger from Slack or the Web UI and ends with a comprehensive service health report. It coordinates six domain-specific sub-agents encompassing the areas of incident management, deployment, application, database, infrastructure, and external APIs. Each sub-agent pulls the relevant signals and runs targeted checks, producing detailed findings. The supervisor then synthesizes these into an investigation-ready brief. The brief contains a concise summary of suspects and blast radius, timeline, and recommended next steps. The briefs are grounded in logs and metrics, so engineers can quickly understand the impact and move toward resolution.
Users can inquire via Slack or the Web UI to receive an immediate, evidence-supported action plan. Examples of such questions include:
Powered by our SuperAgent and MCP tool layer, dynamic chat queries live systems such as metrics, logs, deploy history, and configs. It then returns cited data, comparisons, and next-best actions. On-call engineers can diagnose issues and pull logs on the fly, before escalating actions (e.g., open a ticket, compare regions, list owners, suggest rollbacks). It’s human-in-the-loop (HITL) by design.
The Kinabalu MCP Toolkit serves as a universal integration layer that empowers AI SRE by unifying 25 operational tools into a single, consistent interface. This comprehensive toolkit spans six key domains:
The Kinabalu MCP Toolkit is designed to provide AI SRE with a 360 degree view of incidents, significantly accelerating root-cause discovery and response.
Our journey highlights the importance of structured context, robust diagnostic layers, and hybrid AI models for dependable incident automation. With Kinabalu AI SRE, we’re moving toward an ecosystem where alerts are normalized, evidence is automatically synthesized, and engineers can focus on higher level decision-making rather than firefighting.
Stay tuned for part 2, where we will cover the challenges, design decisions, and lessons that shaped Kinabalu AI SRE.
Grab is a leading superapp in Southeast Asia, operating across the deliveries, mobility and digital financial services sectors. Serving over 800 cities in eight Southeast Asian countries, Grab enables millions of people everyday to order food or groceries, send packages, hail a ride or taxi, pay for online purchases or access services such as lending and insurance, all through a single app. Grab was founded in 2012 with the mission to drive Southeast Asia forward by creating economic empowerment for everyone. Grab strives to serve a triple bottom line – we aim to simultaneously deliver financial performance for our shareholders and have a positive social impact, which includes economic empowerment for millions of people in the region, while mitigating our environmental footprint.
Powered by technology and driven by heart, our mission is to drive Southeast Asia forward by creating economic empowerment for everyone. If this mission speaks to you, join our team today!
Post Syndicated from Ryan Smith original https://www.servethehome.com/intel-ces-2026-keynote-live-coverage/
After a brief break following NVIDIA’s enterprise-focused keynote, we’re back for our second chipmaker keynote of the day: Intel. Unlike NVIDIA’s presentation, Intel’s presentation promises to be far more on-brand for CES, with a focus on consumer electronics via their Core Ultra Series 3 processors – better known as Panther Lake. Intel CES 2026 Keynote […]
The post Intel CES 2026 Keynote Live Coverage appeared first on ServeTheHome.
Post Syndicated from Ryan Smith original https://www.servethehome.com/nvidia-launches-next-generation-rubin-ai-compute-platform-at-ces-2026/
CES may still informally be the Consumer Electronics Show. But that does not mean everyone got the memo – or at least, cares to pay attention to it. Case in point is NVIDIA, who in the first major chipmaker press conference of the day opted for nothing less than to announce the launch of Rubin, […]
The post NVIDIA Launches Next-Generation Rubin AI Compute Platform at CES 2026 appeared first on ServeTheHome.
Post Syndicated from Matthew Garrett original https://mjg59.dreamwidth.org/74084.html
Hello! I am not posting here any more. You can find me here instead. Most Planets should be updated already (I’ve an MR open for Planet Gnome), but if you’re subscribed to my feed directly please update it.
comments
Post Syndicated from Satesh Sonti original https://aws.amazon.com/blogs/big-data/simplify-multi-warehouse-data-governance-with-amazon-redshift-federated-permissions/
Modern data architectures increasingly rely on multi-warehouse deployments to achieve workload isolation, cost optimization, and performance scaling. Amazon Redshift federated permissions simplify permissions management across multiple Redshift warehouses.
With federated permissions, you register Redshift warehouse namespaces with the AWS Glue Data Catalog, creating a unified catalog that spans your entire warehouse fleet in the account. Registered namespaces are automatically mounted in every warehouse, providing data discovery without manual configuration. You can define permissions on database objects using familiar Redshift SQL commands, specifying global identities through AWS Identity and Access Management (IAM) or AWS IAM Identity Center (IDC). These permissions are stored alongside the warehouse data and enforced consistently, regardless of which warehouse runs the query. This provides a unified and secure access control model across your Redshift environment.
In this post, we show you how to define data permissions one time and automatically enforce them across warehouses in your AWS account, removing the need to re-create security policies in each warehouse.
Federated permissions in Amazon Redshift offer the following key capabilities:
CREATE RLS POLICY, attach them to tables and roles with ATTACH RLS POLICY, define masking policies with CREATE MASKING POLICY, and grant permissions with standard GRANT statements. This SQL interface enables infrastructure as code (IaC) approaches, supports database administrators to use their existing skills, and integrates naturally with existing extract, transform, and load (ETL) and automation workflows that use IAM or IAM Identity Center authentication.The multi-warehouse architecture with federated permissions in Amazon Redshift represents a data mesh approach where multiple independent compute resources operate on shared data with unified governance. The following diagram illustrates the Redshift federated permissions setup process with the Data Catalog.
The process consists of the following steps:
database@catalog_name.schema_name.table_name.The enforcement of fine-grained access controls on remote data is a key differentiator of federated permissions. Traditional Redshift data sharing doesn’t support RLS or DDM policies on shared tables. With federated permissions, the security policies defined on the remote warehouse automatically apply when data is queried from any consumer warehouse. This supports compliance with data governance requirements without requiring administrators to duplicate security policies across warehouses.
The multi-warehouse architecture scales horizontally without increasing governance complexity. When you add a new warehouse to your account and register it with federated permissions, it automatically inherits the appropriate permission model without manual configuration. Analysts connecting to the new warehouse immediately see all databases they have access to across the mesh, and all security policies apply automatically. This alleviates the N-squared problem of managing permissions across N warehouses, reducing the administrative burden from N separate configurations to a single unified governance model.
The following diagram illustrates the step-by-step flow of how a user query on Redshift Warehouse 1 accesses objects in Redshift Warehouse N with federated permissions.
Note: Steps 2, 3, and 4 will be skipped if permission details are available in the local cache
The workflow consists of the following steps:
GetTable API. This request includes the user’s token.The example in this post demonstrates how to define RLS and DDM policies on a data warehouse and verify that these policies are enforced when querying from another data warehouse.
We will create a table with credit card data and apply RLS and DDM policies to limit consumer cards data and mask credit card values for non-admin users. These policies will be applied across all the data warehouses consistently and mask the credit card details when non-admin users query the table.
Create the following IAM roles:
Admin role with the AmazonRedshiftFullAccess policy and grant sys:superuser or sys:secadmin role access.Readonly role with the AmazonRedshiftQueryEditorV2ReadSharing policyRun following steps to create a credit_card table and load sample data.
Run following steps to create and apply RLS and DDM policies.
Run following steps on data warehouse 2 to query the data.
credit_cards table from data warehouse 1 when you expand the catalog.
rs-demo-dw1 in the following SQL with the catalog name you gave while registering data warehouse 1:
consumer type credit cards with card details masked in the output. The RLS and DDM policies applied in data warehouse 1 on the IAMR:ReadOnly user are enforced even though you queried the table from a different data warehouse.
SHOW commands to view the policies applied on the tables for the roles:
This example demonstrates the power of federated permissions: security policies defined one time on a warehouse automatically enforce across your warehouses, maintaining compliance without duplicating policy definitions.
Keep in mind the following when using federated permissions:
To avoid incurring future charges, delete the resources you created, including the Redshift data warehouses and IAM roles.
Amazon Redshift federated permissions transform multi-warehouse data governance into a streamlined, automated process. For organizations operating multiple Redshift warehouses, federated permissions deliver immediate value by reducing administrative time and supporting consistent security enforcement. The familiar SQL interface and backward compatibility with existing Redshift permissions enable rapid adoption without requiring teams to learn new governance models.
The integration with IAM and IAM Identity Center provides enterprise-grade identity management with SSO capabilities, and the automatic mounting of registered catalogs simplifies data discovery and cross-warehouse analytics. If you are currently using Amazon Redshift local permissions, refer to the tool described in Modernize Amazon Redshift authentication by migrating user management to AWS IAM Identity Center.
To learn more and get started, see Amazon Redshift Federated Permissions documentation.
Post Syndicated from The Atlantic original https://www.youtube.com/shorts/ZMW60vfGGwQ
Post Syndicated from Ryan Smith original https://www.servethehome.com/nvidia-ces-2026-keynote-live-coverage/
CES 2026 is here! Kicking things off for the major chipmakers today is NVIDIA, who is at the show to talk about all things AI – a hot topic across the entire industry at the moment. NVIDIA CES 2026 Keynote Live Coverage Preview As with most of NVIDIA’s major presentations, company CEO (and leather jacket […]
The post NVIDIA CES 2026 Keynote Live Coverage appeared first on ServeTheHome.
Post Syndicated from Spencer McIntyre original https://www.rapid7.com/blog/post/pt-metasploit-2025-annual-wrap-up
Hard to believe it’s that time again, and that Metasploit Framework will see the dawn of another Annual Wrap-Up (and a New Year). All of the metrics and modules you see here would in large part not be possible without the dedicated community members who care about the Framework and its mission on all the days of the year. It is their hard work and dedication that makes it look like magic, and sometimes, it feels like it too. A heartfelt thank you to all of our researchers and contributors, you’re what makes Metasploit Framework so resilient.
This year brought its share of notable vulnerabilities, substantial framework improvements, and continued evolution of the project. Whether you submitted a module, filed an issue, or helped triage a bug, your contributions have kept Metasploit relevant and powerful. So without further ado, let’s dive into the highlights from 2025.
One of the year’s significant infrastructure improvements came from community contributor h00die, who spearheaded a massive refactor of Metasploit’s persistence modules. The project, tracked in issue #20374, involved reorganizing dozens of persistence modules from their scattered locations across the framework into a dedicated persistence directory under exploits. This wasn’t just housekeeping—h00die created a standardized persistence mixin that brought consistency to how modules handle installation, cleanup, and option handling. The refactor touched over 30 modules spanning Linux, Windows, OSX, and multi-platform techniques, modernizing each one with proper check methods, MITRE ATT&CK references, and standardized options like WritableDir. The work also laid the groundwork for a persistence suggester module that can automatically recommend viable persistence techniques based on session characteristics.
The sheer scope of this effort can’t be overstated. Breaking the work into manageable chunks, h00die systematically converted modules from the old post-exploitation style to proper exploit modules with the new persistence mixin, handling everything from cron jobs and SSH keys to Windows registry modifications and service installations. The standardization means that all persistence modules now share common behaviors, produce cleanup scripts in a consistent format, and integrate cleanly with the rest of the framework. It’s the kind of unglamorous but essential work that improves the entire framework’s usability and maintainability, and we’re grateful to h00die for taking on such an ambitious project and seeing it through.
This year, Metasploit expanded its Active Directory Certificate Services (AD CS) coverage by adding detection and exploitation support for certificate templates vulnerable to ESC9, ESC10, and ESC16. Checks for these misconfigured certificate templates were integrated into the existing ldap_esc_vulnerable_template module, allowing users to easily identify misconfigured templates during assessments.
To complement this detection capability, we introduced the new esc_update_ldap_object module, which enables reliable exploitation of these vulnerable templates to escalate privileges. ESC9, ESC10, and ESC16 share a common pattern: each requires control of a user account with write privileges over another user that is permitted to enroll in the vulnerable template. While exploiting these techniques with other tools typically involves multiple manual and error-prone steps, the new module streamlines the entire workflow. Users configure the required datastore options, run the module, and receive a certificate that can be used to escalate privileges within the domain.
As part of this effort, we also introduced the ldap_object_attribute module, which provides standard CRUD operations for manipulating LDAP objects in Active Directory. This module — along with existing functionality such as shadow_credentials and get_ticket — is used internally by esc_update_ldap_object to abstract away low-level LDAP interactions and simplify exploitation.
This work included comprehensive documentation covering the configuration of templates vulnerable to ESC9, ESC10, and ESC16, as well as detailed instructions for exploiting each technique using the new module.
Related to our AD CS improvements, came new low-level functionality for interacting with Active Directory (AD) Domain Controllers over LDAP. Over the past couple of years, Metasploit has seen multiple modules added that facilitate AD attack workflows including Shadow Credentials, RBCD, Unconstrained Delegation, etc. Like the AD CS attacks, many of these techniques are reliant on access control to some degree. Over the summer, Metasploit introduced new functionality to facilitate checking for these types of attacks. This new library provides Active Directory specific functionality, most notably, the ability to remotely evaluate security descriptors to determine whether a particular user or group has a specific access right. This has already been incorporated into the following modules to either enable or improve the existing detection capabilities.
For module authors, the library provides a composable API for determining if an object grants a particular permission to an optional SID. The SID can be either a user or group, and when omitted is automatically set to the authenticating user, i.e. to check if the current connection has the permissions.
For example, check if the object grants the read and write property permissions with:
adds_obj_grants_permissions?(@ldap, obj, SecurityDescriptorMatcher::Allow.all(%i[RP WP]))
Beyond new features and modules, 2025 also saw substantial code quality improvements thanks to community contributor bcoles, who took on the often-thankless task of resolving RuboCop violations across the codebase. Throughout the year, bcoles systematically worked through older modules, cleaning up style inconsistencies, fixing syntax violations, and converting outdated property types to proper boolean values in auxiliary scanners and exploit modules. This kind of incremental maintenance work—fixing redundant parentheses here, resolving style violations there—doesn’t make for flashy headlines, but it keeps the codebase maintainable and makes life easier for everyone working in the framework. Code quality matters, and we’re grateful to bcoles for putting in the work to keep Metasploit’s technical debt in check.
It may be a fun fact, or perhaps tribal knowledge that an “exploit” to Metasploit is a module that delivers a payload. All the great exploit content this year would be nothing without corresponding payloads to deliver and we make sure that those get plenty of our time as well. The following changes in particular are highly impactful and may have gone unnoticed while the flashier exploits received all the attention.
The biggest updates for the Windows Meterpreter revolve around two major improvements: the first is the upgrade to ReflectiveDLLInjection, made by Alex (xaitax) Hagenah, for which we express our gratitude for improving this area of the Metasploit Framework that requires a high level of attention to detail. This update introduces full, production-ready ARM64 support and a comprehensive architectural modernization of the whole library. These changes open the door to future support for a native ARM64 Meterpreter on Windows. Additionally, Metasploit split the standard API extension for Windows this year. This was actually the design used in the original Meterpreter implementation and we’ve reconsidered the monolithic approach. This improvement is one of the multiple steps we have in the pipeline to improve the evasion capabilities for our Windows Meterpreter. The standard API library now allows the user to load only specific subcomponents of the extension (for example, the component for network or file-system interaction), reducing the memory footprint for memory scanners. To leverage this new functionality, set AutoLoadStdapi to False, and then load one or more extensions manually, e.g. load stdapi_fs. To maintain backwards compatibility, a single stdapi extension is also still available and can be loaded with load stdapi.
The first milestone was the introduction of fileless execution for Linux fetch payloads, enabling payloads to run directly from memory using anonymous files. This advancement greatly enhances operational stealth by minimizing forensic traces and avoiding file-based detection, with careful attention to safe, opt-in behavior and collaborative code refinement. Following this, the FETCH_PIPE option streamlined payload deployment into a single, compact command. This improvement enhanced both usability and evasion, while also supporting larger, more complex command payloads (such as fileless execution) to be executed even with reduced command size. Additionally, fetch payload support has expanded to seven additional CPU architectures: aarch64, armbe, armle, mipsbe, mipsle, ppc, and ppc64le. This significantly broadens Metasploit’s reach across embedded and legacy systems. Both features are thoroughly tested and future-proof, making the framework more versatile and powerful.
This year, we have also updated the framework to support new basic payloads. We have introduced the exec payload for Windows ARM64 (provided by Alex (xaitax) Hagenah), reverse shell for RISC-V 32 and 64 bit, and Loongarch64 (both provided by bcoles).
As much as we try, everything doesn’t always fit into one year. With that in mind, we wanted to highlight some upcoming features that we’re particularly excited to complete in the coming months.
The malleable c2 will allow the user to specify with a .profile scribing how the HTTP requests between meterpreter and metasploit-framework should look like, allowing metasploit to hide the distinctive traffic generated by the session communication.
We have updated the Meterpreter core (metsrv) to remove common static signatures, such as specific strings and function imports, making it harder to detect.
Additional work to port the poolparty injection on native 32 bit system, Huge thanks to xHector1337 for taking over the research and extension of the code injection for the new architecture.
This year, Metasploit added two modules for targeting SCCM instances and recovering the Network Access Account credentials. These modules differ in how they perform the authentication. The first, auxiliary/admin/sccm/get_naa_credentials accepts credentials from the operator and will use them to authenticate and run the attack on demand. This pairs nicely with the auxiliary/admin/dcerpc/samr_account module when the operator can create a new machine account. However, when that’s not an option, Metasploit still has you covered with the auxiliary/server/relay/relay_get_naa_credentials variant that enables relaying NTLM authentication from an SMB server. These attack workflows were demonstrated at Black Hat and DEF CON over the summer and we anticipate they’ll remain useful in the future.
This year, Metasploit significantly leveled up its relaying capabilities, transforming the framework’s only SMB to SMB relay capability into a powerful engine for lateral movement. Traditionally, SMB relaying was often the domain of standalone external tools, but through the dedicated work of the Metasploit team, these workflows are now seamlessly integrated into the framework
A huge thank you from the entire Metasploit team to all 66 contributors in 2025. Your contributions and ideas are what continue to improve this tool every year. Notably, 41 of these were first-time contributors who added new code.
Here are some stats for 2025:
Contributors in 2025 (ordered by count)
Post Syndicated from corbet original https://lwn.net/Articles/1052269/
The calendar has flipped over to 2026; a new year has begun. That means
the moment we all dread has arrived: it is time for LWN to put out a set of
lame predictions for what may happen in the coming year. Needless to say,
we do not know any more than anybody else, but that doesn’t stop us from
making authoritative-sounding pronouncements anyway.
Post Syndicated from Prasad Rao original https://aws.amazon.com/blogs/aws/happy-new-year-aws-weekly-roundup-10000-aideas-competition-amazon-ec2-amazon-ecs-managed-instances-and-more-january-5-2026/
Happy New Year! I hope the holidays gave you time to recharge and spend time with your loved ones.
Like every year, I took a few weeks off after AWS re:Invent to rest and plan ahead. I used some of that downtime to plan the next cohort for Become a Solutions Architect (BeSA). BeSA is a free mentoring program that I, along with a few other Amazon Web Services (AWS) employees, volunteer to host as a way to help people excel in their cloud and AI careers. We’re kicking off a 6-week cohort on “Agentic AI on AWS” starting February 21, 2026. Visit the BeSA website to learn more.
There is still time to submit your idea for the Global 10,000 AIdeas Competition and compete for $250,000 in cash prizes, AWS credits, and recognition, including potential featured placement at AWS re:Invent 2026 and across AWS channels.
You will gain hands-on experience with next-generation AI development tools, connect with innovators globally, and access technical enablement through biweekly workshops, AWS User Groups, and AWS Builder Center resources.
The deadline is January 21, 2026, and no code is required yet. If you’re selected as a semifinalist, you’ll build your app then. Your finished app needs to use Kiro for at least part of development, stay within AWS Free Tier limits, and be completely original and not yet published.
If you haven’t yet caught up with all the new releases and announcements from AWS re:Invent 2025, check out our top announcements post or watch the keynotes, innovation talks, and breakout sessions on-demand.
Launches from the last few weeks
I’d like to highlight some launches that got my attention since our last Week in Review on December 15, 2025:
See AWS What’s New for more launch news that I haven’t covered here. That’s all for this week. Check back next Monday for another Weekly Roundup!
Here’s to a fantastic start to 2026. Happy building!
– Prasad
Post Syndicated from Explosm.net original https://explosm.net/comics/a-priest-a-pastor-and-a-rabbi
New Cyanide and Happiness Comic
Post Syndicated from jzb original https://lwn.net/Articles/1052796/
Version 1.30 of the GNU
ddrescue data recovery tool has been released. Notable changes in
this release include improvements to automatic recovery of a drive
with a dead head, addition of a --no-sweep option to disable
reading of skipped areas, and more.
Post Syndicated from jzb original https://lwn.net/Articles/1052795/
Security updates have been issued by AlmaLinux (tar), Debian (curl and gimp), Fedora (doctl, gitleaks, gnupg2, grpcurl, nginx, nginx-mod-brotli, nginx-mod-fancyindex, nginx-mod-headers-more, nginx-mod-modsecurity, nginx-mod-naxsi, nginx-mod-vts, and usd), Mageia (cups), Red Hat (container-tools:rhel8, go-toolset:rhel8, grafana, and skopeo), and SUSE (dirmngr, fluidsynth, gnu-recutils, libmatio-devel, python311-marshmallow, python312-Django6, rsync, and thunderbird).
Post Syndicated from The History Guy: History Deserves to Be Remembered original https://www.youtube.com/watch?v=iHS907JeCpU
Post Syndicated from Bruce Schneier original https://www.schneier.com/blog/archives/2026/01/telegram-hosting-worlds-largest-darknet-market.html
Wired is reporting on Chinese darknet markets on Telegram.
The ecosystem of marketplaces for Chinese-speaking crypto scammers hosted on the messaging service Telegram have now grown to be bigger than ever before, according to a new analysis from the crypto tracing firm Elliptic. Despite a brief drop after Telegram banned two of the biggest such markets in early 2025, the two current top markets, known as Tudou Guarantee and Xinbi Guarantee, are together enabling close to $2 billion a month in money-laundering transactions, sales of scam tools like stolen data, fake investment websites, and AI deepfake tools, as well as other black market services as varied as pregnancy surrogacy and teen prostitution.
The crypto romance and investment scams regrettably known as “pig butchering”—carried out largely from compounds in Southeast Asia staffed with thousands of human trafficking victims—have grown to become the world’s most lucrative form of cybercrime. They pull in around $10 billion annually from US victims alone, according to the FBI. By selling money-laundering services and other scam-related offerings to those operations, markets like Tudou Guarantee and Xinbi Guarantee have grown in parallel to an immense scale.
Post Syndicated from The Atlantic original https://www.youtube.com/watch?v=Zu8OgAVsJJU
Post Syndicated from Боян Юруков original https://yurukov.net/blog/2026/mestni-danaci/
Наскоро в групите в район Изгрев, София се отвори тема за ремонти с публични средства направени изглежда приоритетно пред новия хотел на 4-ти километър. Писал съм за това преди. Районният кмет отрича да има връзка, но нов асфалт на навярно най-разбитата улица в района е положен буквално до гаражите на сданието, а парк в края на района до булеварда беше направен скоростно точно след като заработи хотела при множество проблемни детски площадки и паркове до училища и градини из целия район.
Има съмнения за доста проблеми около разрешенията на самия хотел, озеленяването му и огромния билборд, който са направили. Обърнаха се към мен обаче в една група с принципен въпрос – как се очаква с толкова ниски местни данъци да се оправят градинки, паркове, детски площадки и цялата инфраструктура.
Отговорът ми се получи доста изчерпателен и тъй като не обичам да обяснявам едно и също на много места, ще го поместя тук с дребни корекции, за да препращам към него в бъдеще. Сложих и няколко линка към стари статии, в които съм разгледал в детайли аспекти от темата.
Новото строителство има задължителна озеленяване, което трябва да се поддържа. Често не се прави въобще или недостатъчно или не по изискванията или просто 2 до 5 години каквото има като зеленина се бетонира за паркоместа. Отговорност на районният кмет е да не го допуска, но не го прави. Подавал съм много сигнали за такива проблеми, но или ги заравя, или зачерква без реални проверки.
Ако се поддържа въобще, както е в комплексите, това идва от таксата на сградата. Решава се от блока, но като цяло не отиват повече от 5 до 20 лв. на месец. Това обаче е само за прилежащата зеленина към имота.
В квартала, където живеех във Франкфурт, нямаше такава такса, каквато говорите. Имаше си такса към блока отново за прилежащата зеленина. Парковете и зеленината в квартала се поддържаха от данъка на жилищата. Всеки град в Германия има различни политики и такси. Често по квартали е различно дори, особено в историческите части. Във Франкфурт имаше дори обществени съвети по квартали, където да се обсъждат и поставят такива теми. Понякога и да се налагат местни такси за определена цел. В някои села, поне в Хесен, карат живеещите според зоната да плащат част от разхода за ремонт на пътища, тротоари и зеленина. Не е пожелателно и стига десетки хиляди. Чел съм за случаи, в които хора продават къщите си заради такива наложени такси.
В София всичко на общинска собственост се поддържа от бюджета на общината. Той идва както от данъците на жилищата, така и от доста други проходи като такси за строителство, продажба или наеми на общински имоти за сгради, търговски площи и билбордове и прочие. Голяма част идва директно от държавния бюджет, както и конкретни целеви програми – предимно за инфраструктура. От същият бюджет идва чистенето на улиците, махането на снега и прочие.
Дали софиянци биха се съгласили на нова такса е спорно. Повечето по-скоро не, защото не смятат, че ще се използва рационално. Пример са таксите и глобите за паркиране, които трябваше да отиват за оправяне на тротоари и пътища, но потъват предимно в частни ръце заради ръководството на ЦГМ.
В този смисъл проблемът си остава управлението на сегашните приходи и да се покаже на жителите на града, че ако дават повече, ще получават повече. Отделно го има политическия аспект, че СОС в сегашния си формат може и да приеме вдигане на данъците, но предвид историята му ще ги натика в общински фирми с лошо управление, за да изтекат, а вината за това ще прехвърли на общината. Разбира се, харченето на публични средства в полза на няколко едри инвеститори, а не мнозинството живеещи в един квартал, каквито съмнения има нерядко, също разрушава доверието, че се използват целесъобразно. Не на последно място в зависимо какъв данък се вдига, вероятно ще трябват законодателни промени, за да се предвиди новата схема от ставки и намаления за първо жилище и/или необитавани такива.
Определено данък жилища е много нисък. Говори се отдавна за вдигане на процентът от данъчната оценка, особено за второ и трето жилище и такива, в които не се живее. Не бяха приети предложенията, а Конституционният съд излезе преди години с доста странно и изпълнено със съмнения за лобизъм решение, че не можело данъка да зависи от използването на даден имот. Миналата година имаше инициатива да се преизчислят данъчните оценки на реални пазарни цени, защото сега са многократно по-ниски, но беше блокирано отново от икономически интереси. Местните данъци и много други такси се изчисляват на база данъчна оценка. Та има много законодателни и нормативни инициативи за това, но се блокират по политически или лобистки причини в СОС и НС.
Друг важен детайл е, че в София много зелени площи всъщност са частни, а не държавни. Особено междублокови пространства. Затова направих карта на известната собственост в 25 български града, за да може всеки от нас да провери. Общината няма задължение, а в известен смисъл и право, да поддържа тези площи. Понякога хора от квартала се хващат и ги оправят, включително с пейки и алеи. След това се появява собственика, загражда и строи. Има отново редовно инициативи да се изкупят тези пространства, както и аналогични в паркове, но са нужни милиарди евро за целта. Имаше шанс да струват стотици милиони и по-малко ако по времето на Фандъкова бяха използвали възможност в закона преди повече от 5 г., но отчасти нарочно не беше направено.
Иначе детските градини и инфраструктура се плащат често от държавния бюджет или европрограми. Компенсациите за неприемане на дете в градина или ясла, например, са от държавния бюджет. Има и доста държавни имоти, за които отговаря държавата или държавни фирми, но буренясват.
Още информация по тази тема:
Post Syndicated from Ryan Smith original https://www.servethehome.com/asus-ascent-gx10-review-a-new-nvidia-gb10-solution/
Asus has released their NVIDIA GB10-based mini-PC, the Ascent GX10. Based on NVIDIA’s powerful Spark platform, the GX10 offers a large amount of high-end AI hardware in a tiny box
The post ASUS Ascent GX10 Review A New NVIDIA GB10 Solution appeared first on ServeTheHome.
Post Syndicated from corbet original https://lwn.net/Articles/1052732/
The 6.19-rc4 kernel prepatch is out for
testing.
So this rc is still a bit smaller than usual, but it’s not _much_
smaller, and I think next week is likely going to be more or less
back to normal.Which is all exactly as expected, and nothing here looks
particularly odd. I’ll make an rc8 this release just because of the
time lost to the holidays, not because it looks like we’d have any
particular issues pending (knock wood).