897 karma · joined March 8, 2016
Quote:
> The affected packages are frontend libraries that are compiled and bundled into some container images during the Red Hat product build process.
So you might be affected if you deployed any Red Hat container images built after the compromise, I guess. (I doubt anyone besides Red Hat is using the affected packages directly.)
https://deepsid.chordian.net/?file=/MUSICIANS/G/Galway_Marti...
(use the little up/down arrows to switch between subtunes)
$ cat l.sh
alias l=ls
l
$ sh l.sh
file1 file2 l.sh
$ bash l.sh
l.sh: line 2: l: command not found
$ bash -i l.sh
file1 file2 l.sh
Edit: Ah yes, the man page says so.> Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt
https://www.cwa.gov.tw/V8/E/E/EQ/EQ113019-0403-075809.html
And a list of all recent earthquakes, showing the aftershocks:
Or if they have access to, or can subpoena, a MitMaaS for HTTPS. Like Cloudflare.
> Rosetta doesn’t support the bootstrapping or installation of Intel Linux distributions on Mac computers with Apple silicon using the Virtualization framework.
So I guess it still won't be possible to run RHEL (or derivative) VMs on Apple Silicon. (Their aarch64 images don't work, something obscure with page size IIRC. Odd because Debian/Ubuntu's aarch64 work fine.)
Edit: Looks like RHEL9 has changed page size so it can run as a VM on Apple Silicon. Unfortunately my common use case for VMs is to prototype things for production, and that's all on RHEL7/8. :(
It depends on the frequency. Occasional CEs are somewhat expected (on a large enough scale) and one can live with them, after all that's what ECC is for. When CEs start happening frequently on one machine, most likely a DIMM is going bad and will worsen over time, so one should replace it.
On server-class machines, ECC errors often also show up in the system event log, so one can run "ipmitool sel list" and inspect the most recent messages, and they often point to the failing DIMM in a nomenclature that corresponds to how the slots are labelled on the mainboard or in its manual.
In this case, they are using a "gaming" mainboard, so this strategy probably doesn't work (no nice system event log).
The Julia equivalent is:
julia> ((((2^2)^2)^2)^2)^2
4294967296
Julia's ^ is right-associative.That said, this attack may be able to extract other information from system memory that would enable de-facto root access, it depends a lot on what's running on the machine.
> What can we do?
Install the patches and enjoy the reduced performance. Or run Linux on ARM, and hope that noone will find similar exploits in the ARM architecure.
Edit: I see that V5 is the upstream default since "only" ~2015, so indeed there are likely many V4 filesystems still around.
Then again, in scientific computing, often these are the same person.
According to this, Google wants to drop Manifest v2 support in Jan 2023.
Umm, there are now almost daily threads on HN about how bad Google search has become, especially for product search... So I'd guess many people will be happy about a no-nonsense offering from a somewhat reputable manufacturer like Logitech.
I'm aware of randomized algorithms with better complexity, which come at the cost of only giving approximate results (though the approximation may be perfectly good for practical purposes). See e.g. [1]. Are there other approaches?
Then again, people that use password managers at all usually have stronger passwords and less password reuse, so it can be an acceptable tradeoff.
1. Vimeo responds to the original request with "will look into it", then... nothing happens? This may depend on culture, but at least from my experience in the UK, this is a very non-committal response, and if you really want them to do something, you'll need to chase them. Wait a few days and inquire if they have any estimate for when it might get done, or if they need more information. I find that the "looking into it" response is sometimes used to gauge how important the request is to you.
2. Once you go with your own solution, just drop a quick message to Vimeo: "Hey, just wanted to let you know we've found our own solution for this, and won't require your help any more. Sorry if you've already committed any resources for this task. Have a nice day, yada yada." This not just avoids what happened here, but is also a courtesy to them.
Current example: https://news.ycombinator.com/item?id=31248250