matja

It lives on in spirit, having heavily influenced the design of ZFS and its admin interface:

    advfs addvol -> zpool add
    advfs advscan -> zpool import
    advfs clonefset -> zpool clone
    advfs mkfset -> zfs create
    advfs rvdump -> zfs send
    advfs rvrestore -> zfs receive
    advfs showfsets -> zfs get/list
    advfs verify -> zpool scrub

* Shared bandwidth between CPU and GPU - as soon as you use up one, you're bottlenecking the other.

* No M2 memory benchmark I've seen gets above ~250GB/s once cache effects are exceeded.

* Random access latency is >~110ns which is no improvement over even mid-range DDR4 designs from 5 years ago.

TL;DR: It's about cost

AZ is a term used by AWS and Azure. GCP documentation makes it clear to "Distribute your resources across multiple zones and regions", where regions are physically different data centers.

Reminds me of TheRasteri's video on using an EEPROM to convert CGA TTL video signals to EGA/VGA : https://www.youtube.com/watch?v=vwKA1z8tg1g&t=261s

But in the POC link, they have state=1 as a parameter for the authorization server, there is another state parameter encoded into the value for the redirect_uri, which makes me wonder why that even matches the registered redirect_uri.

Interesting, thanks!

I agree the fact that Harvest blindly redirects helps enable the attack, but according to the OAuth standard, a redirect_uri which does match a registered one should not be accepted before authorization takes place.

From the POC authorization URL, the redirect_uri parameter and value are:

    redirect_uri=https%3A%2F%2Foutlook-integration.harvestapp.com%2Fauth%2Foutlook-calendar%2Fcallback?state=%7b%22return_to%22:%22/time%22%2c%22subdomain%22:%22example.com/%22%7d

So if Harvest registered the redirect_uri as:

    https%3A%2F%2Foutlook-integration.harvestapp.com%2Fauth%2Foutlook-calendar%2Fcallback

then why does any extra URL parameters added to that value get accepted by the Microsoft OAuth server before authorization, when they clearly do not match the registered one?

edit: I tried authorizing using another OAuth server provider, with a changed redirect_uri by appending URL parameters to the encoded value, and the OAuth server (I believe, quite rightly) rejected the authorization request.

RFC 6749 goes into details on how the authorization server should prevent this type of attack

    The authorization server MUST require public clients and SHOULD require
    confidential clients to register their redirection URIs.  If a redirection
    URI is provided in the request, the authorization server MUST validate it
    against the registered value.

So how is this possible, when presumably the Harvest app did not register the malicious redirect_uri?

Does the Microsoft OAuth server ignore URL parameters within a redirect_uri when comparing with registered redirect URIs for the OAuth client?

It's missing the timezone offset

By the wording of the RFC, accepting a hostname longer than 255 bytes is permissible, creating one is not.

That was a thing: https://en.wikipedia.org/wiki/TCP_Port_Service_Multiplexer

Exactly. How many gramattically correct sentances are there, vs what is the probability that a "random" hash used as an EC seed results in poor security? Research[0] has demonstrated it's not a theoretical vulnerability in the EC selection process.

[0] https://bada55.cr.yp.to/bada55-20150927.pdf

.max file format is intentionally hostile to developers to implement it, forcing them to use the proprietary library/environment. In my experience .obj (binary or ASCII) or .lwo have the best interoperability.

800 MA⁻²·kg·m³·s⁻³!

Ah in that case, base58 can be useful because it doesn't use characters that may be ambiguous in some fonts (doesn't use: 0/O/I/l , but does use: 1/i)

Curious on the preference there, especially when characters in base64url encoding can look similar/ambiguous in some fonts.

I'd just be aware that XFS has no data journaling, only metadata.

Depends on the ABI which the compiler targets. The vast majority of 64-bit OS's are ILP32, LLP64 or LP64, where ints are 32-bit - but to the paper's point, you don't know until you compile it.

> losing SELinux labels makes it difficult to restore a backup of the root filesystem on distros that use SELinux

True, but one should get into the practice of creating persistent policies rather than ad-hoc `chcon`'s all the time, so that a `restorecon -FR /` always restores all SELinux labels to the intended state, then the biggest hassle is just booting into initramfs shell to mount rootfs and `touch /.autorelabel`

The loading routines from that era just count the number of DC zero-crossings and convert X crossings into a 0 and Y crossings into a 1, they don't care about frequency or amplitude (the raw signal is usually fed into a Schmitt trigger to implement hysteresis for a stable edge). That way, the polarity of the tape signal and the variation of the motor is compensated for.

EPROMs, and the UV lamp is locked in a cupboard with a highly secure combination lock

Coincidence?

    $ TZ=UTC date --date=@$[$(date +%s)*2]
    Wed 31 Mar 15:33:50 UTC 2077

= 3.18 W

ASRockRack make a deep MicroATX Genoa and EATX/EEB boards too, which can take up to the 128 core Bergamo EPYC, or the high-frequency "F"-SKUs : https://www.asrockrack.com/general/productdetail.asp?Model=G...

Host kernel: 6.1.33-1-lts (Arch) Guest kernel: 6.4-rc6 defconfig QEMU: 8.0.2 (Arch) CPU: AMD EPYC 74F3

1242 iterations :

  [    0.015088] printk: console [ttyS0] enabled
  [    0.055882] ACPI: Core revision 20230331
  [    0.056124] APIC: Switch to symmetric I/O mode setup
  [    0.056867] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x2e204823bcd,   max_idle_ns: 440795224253 ns
  [    0.057467] Calibrating delay loop (skipped) preset value.. 6399.99 BogoMIPS (lpj=3199998)
  [    0.057924] pid_max: default: 32768 minimum: 301
  [    0.058194] LSM: initializing lsm=capability,integrity
  [    0.058464] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
  [    0.058464] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
  [    0.058464] x86/cpu: User Mode Instruction Prevention (UMIP) activated
  [    0.058464] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [    0.058464] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [    0.058464] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
  [    0.058464] Spectre V2 : Mitigation: Retpolines
  [    0.058464] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
  [    0.058464] Spectre V2 : Spectre v2 / SpectreRSB : Filling RSB on VMEXIT
  [    0.058464] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [    0.058464] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
  [    0.058464] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl
  [    0.058464] Freeing SMP alternatives memory: 48K
  *** ERROR OR HANG ***

After reverting commit f31dcb152a3d0816e2f1deab4e64572336da197d :

40000 iterations (4 runs) = "test ok"

Aesthetics, sure, functionality not so much - the 0 and O characters are identical...

Kioxia CD8 : https://www.storagereview.com/news/kioxia-cd8-series-pcie-5-...

Are they really JPEGs and MP3s, or just bitrot?

I've found https://github.com/ImpulseAdventure/JPEGsnoop useful to fix corruption but I haven't come across a non-standard JFIF JPEG unless it was intentionally designed to accommodate non-standard features (alpha channel etc).

> For double or triple parity, we use a special case of Reed-Solomon coding

https://github.com/openzfs/zfs/blob/zfs-2.1-release/module/z...

Interesting language, "more than 50%". I guess the real number doesn't look good for marketing.