Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Submission Summary: 0 pending, 2 declined, 4 accepted (6 total, 66.67% accepted)

Submission + - Codon Python compiler gets faster (usenix.org)

rikfarrow writes: In May 2023, I tried out Codon, an Open Source Python compiler. At the time, I had difficulty compiling the scripts I most commonly used, but was excited by the prospect. Python is essentially single threaded and checks the shape (type) of each variable as it interprets scripts. Codon fixes types and compiles Python into compact, executable binaries that execute much faster.

Several things have changed with their latest release: I have successful compiles, the committers have added a compiled version of NumPy (high performance math algorithms), and changed their open source license to Apache 2.

Submission + - User lasers to take over systems (usenix.org)

rikfarrow writes: To hack a system, you need access. Air-gapped systems are isolated from external networks, leading to actions like leaving infected USB drives in the parking lot of the target. But Joe Loughry and Kasper Rasmussen came up with another method: using lasers to inject code.

They built two test rigs, one a simple computer and the other a system with an exposed diode on a serial communication line. They could inject code by shooting lasers into display LEDs on the computer, and insert text in a display. Loughry demonstrated the second hack during USENIX WOOT'24, and the article includes videos of both attacks.

Submission + - Caching is key, and SIEVE is better than LRU

rikfarrow writes: Caching means using faster memory to store frequently requested data, and the most commonly used algorithm for determining which items to discard when the cache is full is Least Recently Used. These researchers have come up with a more efficient and scalable method that uses just a few lines of code to convert LRU to SIEVE.

You may wonder why this algorithm is called SIEVE. The reason is that the “hand” in SIEVE functions as a sieve: it sifts through the cache to filter out unpopular objects and retain the popular ones. We illustrate this process in Figure 7. Each column represents a snapshot of the cached objects over time from left to right. As the hand moves from the tail (the oldest object) to the head (the newest object), objects that have not been visited are evicted. For example, after the first round of sifting, objects at least as popular as A remain in the cache while others are evicted. The newly admitted objects are placed at the head of the queue. During the subsequent rounds of sifting, if objects that survived previous rounds remain popular, they will stay in the cache. In such a case, since most old objects are not evicted, the eviction hand quickly moves past the old popular objects to the queue positions close to the head. This allows newly inserted objects to be quickly assessed and evicted, putting greater eviction pressure on unpopular items (such as “one-hit wonders”) than LRU-based eviction algorithms.

The authors explain how LRU works using quick promotion in the queue and lazy demotion, while SIEVE turns this on it head by using quick demotion and lazy promotion. Code changes required to do this are minimal.

Submission + - CAPTCHAs are just annoying (usenix.org) 2

rikfarrow writes: Researchers at University of California, Irvine, put CAPTCHAs to the test. They hired over a thousand people to test 14,000 CAPTCHAs to determine how long it took to solve them, and compared that to AI solvers.

Our work explores CAPTCHAS in the wild by evaluating solving performance and user perceptions of unmodified currently-deployed CAPTCHAS. We obtain this data through manual inspection of popular websites and a large-scale user study wherein 1, 400 participants collectively solved 14, 000 CAPTCHAS. Results show significant differences between most popular types of CAPTCHAS: surprisingly, solving time and user perception are not always correlated. We performed a comparative analysis of effects of experimental context, focusing on the difference between solving CAPTCHAS directly as opposed to solving them as part of a more natural task, such as account creation... Automated attacks on various CAPTCHA schemes have been quite successful, accuracy of bots ranges from 85% to 100%, with the majority > 96%.

If bots are better at solving CAPTCHAs, why do web site developers still use them? Some CAPTCHAs work better than others and are less annoying.

Submission + - Codon compiler for Python is fast

rikfarrow writes: Researchers at MIT decided to build a compiler focused on speeding up genomics processing, and decided to make their language look like Python. Recently, they have posted their code on GitHub, and I gave it a test drive: https://www.usenix.org/publica....

Codon, like Mojo (https://developers.slashdot.org/story/23/05/07/0544230/swift-creators-company-builds-new-programming-language-mojo---a-python-superset), compiles into an executable, so doesn't suffer from the Global Interpreter Lock that prevents the execution of multiple concurrent thread. Codon also uses static typing, without requiring programmers to annotate their code.

Slashdot Top Deals

If you aren't rich you should always look useful. -- Louis-Ferdinand Celine

Working...