329 karma · joined July 6, 2018
"All of my remaining realisable assets are to be disbursed as follows: the capital, converted to safe securities by my executors, is to constitute a fund, the interest on which is to be distributed annually as prizes to those who, during the preceding year, have conferred the greatest benefit to humankind … one part to the person who, in the field of literature, produced the most outstanding work in an ideal direction;"
Has anyone any insight on this?
https://www.nobelprize.org/alfred-nobel/full-text-of-alfred-...
[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
Think about it:
$ dd if=/dev/zero bs=1 count=10M | gzip -9 > 10M.gzip
$ ls -sh 10M.gzip
12K 10M.gzip
Other than that, why serve gzip anyway? I would not set the Content-Length Header and throttle the connection and set the MIME type to something random, hell just octet-stream, and redirect to '/dev/random'.I don't get the 'zip bomb' concept, all you are doing is compressing zeros. Why not compress '/dev/random'? You'll get a much larger file, and if the bot receives it, it'll have a lot more CPU cycles to churn.
Even the OP article states that after creating the '10GB.gzip' that 'The resulting file is 10MB in this case.'.
Is it because it sounds big?
Here is how you don't waste time with 'zip bombs':
$ time dd if=/dev/zero bs=1 count=10M | gzip -9 > 10M.gzip
10485760+0 records in
10485760+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 9.46271 s, 1.1 MB/s
real 0m9.467s
user 0m2.417s
sys 0m14.887s
$ ls -sh 10M.gzip
12K 10M.gzip
$ time dd if=/dev/random bs=1 count=10M | gzip -9 > 10M.gzip
10485760+0 records in
10485760+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 12.5784 s, 834 kB/s
real 0m12.584s
user 0m3.190s
sys 0m18.021s
$ ls -sh 10M.gzip
11M 10M.gziphttps://www.percona.com/blog/2018/03/01/visualize-this-mysql...
For a complete example, see this codesandbox.
Or to sum up:
"Briar is a messaging app designed for activists, journalists, and anyone else who needs a safe, easy and robust way to communicate. Unlike traditional messaging tools such as email, Twitter or Telegram, Briar doesn't rely on a central server - messages are synchronized directly between the users' devices. If the Internet's down, Briar can sync via Bluetooth or Wi-Fi, keeping the information flowing in a crisis. If the Internet's up, Briar can sync via the Tor network, protecting users and their relationships from surveillance."
[1] https://www.goettinger-tageblatt.de/Nachrichten/Panorama/Goe...
[2] https://www.goettinger-tageblatt.de/Nachrichten/Panorama/Goe...
Update: Around 7000 people were evacuated before the disarming took place.
[1] https://www.cloudflare.com/learning/ssl/lava-lamp-encryption...
Real Source: https://curlicuecal.tumblr.com/post/175362924100/an-entomolo...
In fact, Enso OS is pretty much a mix of Xubuntu and elementaryOS:
> The window manager is a fork from gala https://github.com/nick92/Enso-OS/tree/master/galal
> The Greeter is a fork of pantheon-greeter https://github.com/nick92/Enso-OS/tree/master/greeter
> The application menu is a fork of slingshot-launcher https://github.com/nick92/Enso-OS/tree/master/panther_launch...
> It also uses elementaryOSs AppCenter (renamed to App Hive) https://github.com/nick92/apphive
Matthew Ahrens[1]:
…Being "upstream" is more a matter of degree than an absolute ordering. In the past, most ZFS features have originated in illumos, and those changes have been ported to the other platforms (notably FreeBSD and ZoL). Looking forward, we see more features originating in ZoL. The OpenZFS community (including FreeBSD) is working to put in place technical processes to ensure that new ZFS features are available on all platforms. The original post in this thread was a proposal for how to do that.
Alan Jude[2]:
…The way that things have evolved over the last few years means it would be much more difficult to just import changes from ZoL. ZoL was originally far behind the OpenZFS repo, but as they were catching up, they were also fixing bugs and adding features. So there is not really a common point in the source we could start from to import ZoL commit by commit.… The biggest thing to remember is that this is still OpenZFS, and still run by the same developers as it has been. We are just commonizing on the repo that has the most features integrated into it.
[1] https://lists.freebsd.org/pipermail/freebsd-current/2018-Dec...
[2] https://lists.freebsd.org/pipermail/freebsd-current/2018-Dec...
I'd be more interested to see comparison to, for example, Realm[1].
hexdump -C cuedevres.bin | head -12
00000000 71 72 65 73 00 00 00 02 09 d5 35 27 00 00 00 14 |qres......5'....|
00000010 09 d5 15 35 00 04 10 9c ff d8 ff e1 0f 39 45 78 |...5.........9Ex|
00000020 69 66 00 00 4d 4d 00 2a 00 00 00 08 00 07 01 12 |if..MM.*........|
00000030 00 03 00 00 00 01 00 01 00 00 01 1a 00 05 00 00 |................|
00000040 00 01 00 00 00 62 01 1b 00 05 00 00 00 01 00 00 |.....b..........|
00000050 00 6a 01 28 00 03 00 00 00 01 00 02 00 00 01 31 |.j.(...........1|
00000060 00 02 00 00 00 22 00 00 00 72 01 32 00 02 00 00 |....."...r.2....|
00000070 00 14 00 00 00 94 87 69 00 04 00 00 00 01 00 00 |.......i........|
00000080 00 a8 00 00 00 d4 00 0a fc 80 00 00 27 10 00 0a |............'...|
00000090 fc 80 00 00 27 10 41 64 6f 62 65 20 50 68 6f 74 |....'.Adobe Phot|
000000a0 6f 73 68 6f 70 20 43 43 20 32 30 31 37 20 28 57 |oshop CC 2017 (W|
000000b0 69 6e 64 6f 77 73 29 00 32 30 31 37 3a 30 39 3a |indows).2017:09:|
It looks like cuedevres.bin is more of a source file for cueres.bin. It would be interesting if you would rename it and see if iCue is still working.About 72M comes from the directories plugins (some pngs), GameSdkEffects, driver and QtQuick[1]:
~/Downloads/Program Files/Corsair/iCUE du -d1 -h | sort -rh
421M .
28M ./plugins
19M ./GameSdkEffects
13M ./driver
12M ./QtQuick
5.4M ./sounds
5.2M ./translations
3.2M ./System
1.4M ./imageformats
1.2M ./QtGraphicalEffects
1.2M ./platforms
406K ./predefined_data
367K ./QtMultimedia
358K ./mediaservice
286K ./QtQuick.2
265K ./scenegraph
134K ./QtQml
130K ./audio
105K ./Qt
77K ./legal
33K ./iconengines
25K ./playlistformats
The bulk comes from these files: ~/Downloads/Program Files/Corsair/iCUE ls -shS | head -10
total 333M
158M cuedevres.bin
51M cueres.bin
36M iCUE.exe
16M opengl32sw.dll
14M vcredist_x86.exe
4.8M Qt5Gui.dll
4.8M efm8load.exe
4.7M Qt5Core.dll
4.4M Qt5Widgets.dll
The bin files are identified as: ~/Downloads/Program Files/Corsair/iCUE file *.bin
cuedevres.bin: Qt Binary Resource file
cueres.bin: Qt Binary Resource file
manifestres.bin: Qt Binary Resource file
So, it's mostly the QtQuick framework.