Playable Counter-Strike Diffusion World Model (trained on 2x4090, 5M frames)
Article, Comments

We train a diffusion model to predict the next frame of the game. The diffusion model takes into account the agent’s action and the previous frames to simulate the environment response.

> we got AI real time generated games before gta6

git can be extremely dumb sometimes

Yesterday Chinese researchers from Shanghai University unveiled a technique to defeat RSA and AES encryption using Quantum Computing.

The paper titled: "Quantum Annealing Public Key Cryptographic Attack Algorithm Based on D-Wave Advantage", is in Mandarin and has lots of maths

“Using the D-Wave Advantage, we successfully factored a 22-bit RSA integer, demonstrating the potential for quantum machines to tackle cryptographic problems,” the researchers wrote in the paper.

You can either read what other journalists wrote, or you can try to read it yourself.

The original paper: http://cjc.ict.ac.cn/online/onlinepaper/wc-202458160402.pdf

Article

SSL certificate lifetimes are going down. Dates proposed. 45 days by 2027
Article, Comments

MP3 to EXE (1999) (yeah, it's funny at 2024😂)
Article, Comments

The idea is to enable songs to be distributed with no concern whether the recipient will have an MP3 player installed (which was a valid concern in the late nineties. Certainly not a concern anymore for any modern operating system).

Ichigo: Local real-time voice AI
GitHub, Comments

It has very interesting references:

1. Chameleon: Mixed-Modal Early-Fusion Foundation Models
2. Adam-mini: Use Fewer Learning Rates To Gain More
3. High Fidelity Neural Audio Compression
4. WhisperSpeech: An Open Source Text-to-Speech System Built by Inverting Whisper

Try googling this:

yahoo_site_admin/credentials/db.conf

DO NOT FORGET PEOPLE:

1. DISABLE your webserver's Directory Listing feature (at the very least on prod)
2. DISABLE your swagger/openapi route (at the very least on prod); usually at /docs or /swagger (if it's generated automatically, like FastAPI framework does it).
3. RESTRICT access to *.config, *.conf, *.db, *.cfg, etc etc... if you are using an unknown or outdated webserver.

current versions of these webservers are known to be safe for "path traversal vulnerability" by default:
1. nginx
2. IIS
3. Apache

but make sure they are not misconfigured, otherwise (same as the examples above), they might leak sensitive information (resulting in a information disclosure vulnerability).

Helpful links and similar vulnerabilities:
1. CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
2. CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
3. CWE-23: Relative Path Traversal
4. CWE-24: Path Traversal: '../filedir' and CWE-25
5. CWE-34: Path Traversal: '....//' and CWE-35

6. And then there is CWE-36: Absolute Path Traversal which can sometimes literally cause a RCE vulnerability; such as CWE-40: Path Traversal: '\\UNC\share\name\' (Windows UNC Share)

All of these are decades old and no one believes there are still systems which are vulnerable to this; yet just a google search proves that they still do exist 🤦‍♂️