91–100 of 104 posts
Earlier quoted context omitted.
I wonder if using zram or zswap can help "eat" those overly long pointers in RAM via compression ?
I've never understood why zswap decompresses the pages before writing them out to disk. Disk IO is the slowest part of the whole chain, you've already paid to compress the data, why on earth would you throw that away AND use up more disk IO?
Earlier quoted context omitted.
I have a tendency to learn stuff in reverse. I used to make an SD Card ready, connected monitor and keyboard and enabled everything as needed. Then I got the task to deploy n-RPi's and looked at the image first to customize it for the requirements we had. That's when I looked around and saw the unusual unit file and tried to understand why the service would look at the boot partition to start a service. In the end I…
I don’t know the details of how they implement this but it sounds like you want a systemd drop in file to override the ConditionPathExists (or similar) directive (I’m assuming you can’t or don’t want to modify the upstream unit directly given the use of symlinks).
Or you can chroot to the mounted Raspbian root partition and do a normal `systemctl enable ssh` as part of your image customisation. Because, to be clear, you do not have to put a file in /boot to enable SSH, as it was claimed above. That is purely a helpful shortcut.
Earlier quoted context omitted.
Fast table based software AES implementations leak bits of the secret key in array offsets, so anything that can use the cache on the chip can get the key. A software implementation of AES that is secure against side channel attacks by using bitslicing is slow, you would be better off using chacha20-poly1305.
So you're saying OpenSSL might still be using side channel vulnerable AES code, all these years after there was a big row about it? This ARMv8 impl according to comments is constant time: https://github.com/openssl/openssl/blob/master/crypto/aes/as... There are also other ARM AES implementations in the tree: https://github.com/openssl/openssl/tree/master/crypto/aes/as... AFAICT one is for the hardware AES instruction…
Earlier quoted context omitted.
I have heard that AES is very complicated to implement in software, if one intends to avoid side-channel leaks.
You don't, especially not GCM mode. You use one of the mature tested versions out there.
All this was done on a just-for-fun basis, but it ended up just making me frustrated so I stopped trying.
Earlier quoted context omitted.
So that's how they came up with that. As someone who normally installs "normal" Linux systems I find it quite irritating that you have to put a file somewhere, especially the boot record, to "enable" ssh of all things. Up until now I considered it a weird decision. (and I still think it is not optimal) I deploy my RPi's in the field and don't put a monitor on them so I would expect ssh running as default. First time…
Have you considered something like Yocto[0]? I've had good luck with it. [0] https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.h...
Earlier quoted context omitted.
Have you considered something like Yocto[0]? I've had good luck with it. [0] https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.h...
I'm interested in trying it. In the past I used a system based on Debian's Live Build ( https://github.com/gumstix/live-build ) and I was wondering how it differs, but I'm just now noticing even this suggests using Yocto instead.
Earlier quoted context omitted.
Why yes, yes I can: https://www.raspberrypi.org/forums/viewtopic.php?t=252369#p1...
> this will be combined with a 32bit userland, for the reason mentioned above. - the amount of work needed to update all the libraries that talk to the GPU.
One of the main benefits you get to running a proper aarch64 userspace is ability to run a modern functional firefox install. The 32-bit builds usually don't support anything newer than a very old LTS release. It's been hell trying to build and/or run that target (see: https://bugzilla.mozilla.org/show_bug.cgi?id=1452128 ) This is especially important if considering use as a low-end desktop as Chromium will eat throu…
I'm running Firefox 73 on my BeagleBoard-X15 (Cortex-A15). Ubuntu 18.04. $ dpkg -l | grep firefox ii firefox 73.0.1+build1-0ubuntu0.18.04.1 armhf Safe and easy web browser from Mozilla
Slightly off topic, but kind of on theme at least: does anyone know where to get an SBC (single board computer) with 6GB of RAM... or even 4.5GB (that doesn't cost like $~300)? The raspberry PI is almost perfect, I just need slightly more ram per unit. ARM or X86 I really don't care...
You should get an old server rack at that price point unless space is important for you. Udoo - https://shop.udoo.org/udoo-x86-ii-ultra.html LattePanda - https://www.lattepanda.com/products/lattepanda-alpha-864s.ht... There are a few more. You could also build your own. All you need is a micro ITX motherboard + ram and a processor and something to power. Get them used and it will be way more powerful.
I've got a LattePanda v1 but I've been a bit disappointed with it. Udoo bolt is my next test but they're just a bit more expensive than I'd like.
The CPU of the Raspberry Pi 4 is the only 64-bit ARM chip I've ever seen that doesn't include native AES instructions. As a result, it's much lower performance for network or disk encryption use cases. Up until the RPi 4 I thought AES instructions were a part of AArch64, but I was wrong. Such a weird omission to make on (I expect) Broadcom's side. All other 64-bit ARM SBCs just have it, even the low cost ones.
AES is quite efficient in software. The RPi4 should be able to saturate its network connectivity many times over with SW AES. A Pentium II 200 MHz could saturate 100 Mbps with AES-128[1], RPi4 has 4 x 1400 MHz cores (with 64-bit ALU & NEON available). [1] https://www.di.ens.fr/~granboul/recherche/AES/timings.html edit: There are RPi4 AES and other benchmarks here in this "openssl speed" paste: https://gist.github.com…