Effort and RFCs are underway to establish what would become part of TLS protocol stack. One of which is eSNI (encrypted SNI).
56 karma · joined November 28, 2018
Been there done that - SRE/DevOps/SecEng/SysEng/SoftEng
Effort and RFCs are underway to establish what would become part of TLS protocol stack. One of which is eSNI (encrypted SNI).
Woah. Hold your bong son! ;)
Any reference to documentation or any information of what you mean by `sold' on the open market?
If you wanted to prove a point by saying that internet is an insecure medium then yes I agree but `tapped' and `sold' is a whole different ball game that I am not aware of. At least in the internet I know of.
Throwing GDPR and `ftw' in the same sentence. Hmm. No GDPR does not work that way hah. At least not in the global context.
GDPR only applies to you _if_ you happen to be a European Union citizen.
What do you mean by `resource management modeling` in this context? Do you mean `capacity planning` or `system scaling planning` or something else altogether?
Coming from UNIX, used sculpt on QeMU just yesterday. Let me just say this - the exploration was pretty much just `meh`. But also - the devil is in the detail. I bet, if I read the documentation and then go back, I'll stop flaffing around too much and use it to do awesome things.
I loved the ViM though ;)
$ qemu-system-x86_64 -name guest=humbug,debug-threads=on -drive file=/var/lib/libvirt/images/sculpt-vc.qcow2 -machine q35 ....
I fetched their `sculpt-vc.img` and create qcow out of it to directly boot in qemu.
$ qemu-img convert -f raw -O qcow2 sculpt-vc.img /var/lib/libvirt/images/sculpt-vc.qcow2
The resulting image is not bootable. It fails on boot showing Genode logo and goes into a reboot cycle.
$ file sc*
sculpt-vc.img: DOS/MBR boot sector, extended partition table (last)
sculpt-vc.qcow2: QEMU QCOW2 Image (v3), 24375296 bytes
Nice. I'll check it out.
Agreed. APUE is perhaps one of the best book available covering SUS, POSIX layer in detail.
[edit] I have the LDD and https://www.amazon.com/Linux-Kernel-Development-Robert-Love book. I got confused about the authors name :)
The author Robert Love has done a tremendous job on Linux Kernel Development book. Every aspiring "In-betweeners and Low-Low Level engineers" [0] should read this book. It's awwwwespiring.
And please read LDD too!
That's exactly my point as well. Well said - ha at least better than I would be able to explain myself.
- Embarrassingly low-level (chip developers): OS, C/VHDL/Verilog, MA, DS, GPH, EE, Apathy, SE
- The in-betweeners (kernel, device, storage developers): OS, C, MA, DS, GPH, Apathy, Crypto, SE
- Low-Low-level systems: OS, C, DS, GPH, Apathy, Crypto, SE, FTDS, MSG, NW.
- Low-High-level systems: C/Rust, DS, GPH, Apathy, HDS, Crypto, SE, FTDS, MSG, NW, TL.
- Unicorn rock-star systems hacker (perhaps only a handful of these creatures exists :-): Multiple OS, C/Rust/JVM/Erlang/Haskell, Multiple MA, DS, GPH, EE, Crypto, FTDS, MSG, NW, HDS, SSE, TL.
Abbreviations used:
GPH = Good Programming Hygiene
EE = Electronics and Electrical Engineering
OS = Operating System
MA = Modern Assembly
DS = Data Structure
FTDS = Fault-Tolerant Distributed System
MSG = Messaging System
NW = Networking
TL = Toolings (the darlings of UNIX)
HDS = High-Density Systems
SE = Security Engineering