SShortSingh.
Back to feed

FBI Advises Families to Use Secret Code Words Against Voice-Clone Scams

0
·4 views

The FBI has warned that criminals can now create short audio clips mimicking a loved one's voice to request money. To guard against this, the agency recommends that families agree on a secret word or phrase that is not guessable from public social media. The code word should be shared with all family members, including grandparents. If a call seems urgent or unusual, the recipient should ask for the word, since someone using a cloned voice would not know it. The advice appears in an FBI IC3 Public Service Announcement issued December 3, 2024.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How to pack a GitHub repository into an AI-friendly XML file for LLMs

A guide explains how to convert a GitHub repository into an XML-formatted file that can serve as prompt context for LLMs such as Claude, ChatGPT, and Gemini, without using command-line tools. The method works for both public and private repositories and is described as free to use through an online tool called Axleta Repository Packer. Users paste their repository URL and, for private repos, a GitHub Classic Personal Access Token created in their account settings. Optional settings include dynamic .gitignore glob filtering and a choice between a full source mode and a lighter skeleton outline mode for token optimization. The packed output is copied into a text file that can then be attached to an LLM.

0
ProgrammingDEV Community ·

Why Direct Browser Thumbnail Uploads Fail: CORS, Private Buckets, and Presigned Limits

A browser upload to private object storage can fail even with a valid presigned URL, because the browser enforces CORS and the uploaded image still needs authorized delivery. The article advises presigning direct uploads only where the bucket's browser policy is already verified, and otherwise accepting files on the backend and generating thumbnails there. It explains that a presigned URL grants temporary access but does not configure CORS, create a public image URL, or resize images. It also stresses testing the authorization request and the byte transfer separately, and checking the browser preflight, since command-line success does not prove browser compatibility. Finally, it notes that private upload and private display are separate authorizations, with thumbnails served through signed reads or backend proxying.

0
ProgrammingDEV Community ·

Fintech Training Artifact Uploads: Using Signed URLs and Upload Receipts for Private Storage

An on-call engineer facing a missing artifact receipt should halt promotion of the affected training run rather than retry an opaque upload. The article recommends that private fintech artifacts use a backend-generated presigned URL, with bytes uploaded directly from the browser and a separate receipt recorded before the run is marked complete. It compares Supabase Storage, Amazon S3, Cloudflare R2, and Google Cloud Storage, noting which suits frontend-led teams versus platform teams that need full storage controls. It stresses that the storage provider only accepts bytes and serves signed access, while the application must still handle authorization, tenant-to-key mapping, retention, and state transitions. The piece also presents Infrai as an option for consolidating storage and backend services under one key and bill, with CORS handled outside the frontend workflow.

0
ProgrammingDEV Community ·

Envoy xff_num_trusted_hops requires a verified proxy topology to pick the client address

Envoy's original IP detection can derive a client address from X-Forwarded-For, with xff_num_trusted_hops setting how many right-side proxy hops to trust. Per the documentation, with use_remote_address false and N greater than zero, the trusted address is the (N+1)th address from the right. Misreading the counting direction or copying a hop count from another environment can make access rules or rate limits depend on attacker-controlled header values. The count must be updated whenever the topology changes, such as adding a load balancer, ingress layer, or sidecar, and it must be coordinated with use_remote_address across listeners. Teams should map every component that reads or modifies the header, then test with forged headers to confirm which address Envoy selects. Where possible, a single trusted ingress path should overwrite the header and network policy should block bypass routes.