0x44
Joined 18 years ago
Karma
598
Submissions
196
Member since
Mar 14
Joined 18 years ago
If you're already in AWS, your deployment infrastructure and tooling is already configured and tuned for AWS. Deploying a Mac EC2 instance is just adding another target. Whereas deploying to another provider is an unknown amount of work to integrate with their API (if they even have one). The wall-time cost of people's time and effort vastly outweighs the marginal savings you'd get by going with a low-cost provider.
* A protocol that leaks metadata, including some message content, at the envelope layer.
Could you elaborate more on this? I don't really understand what you mean.
He means: EHLO your.mx.example.tld
MAIL FROM:<[email protected]>
MAIL TO:<[email protected]>
DATA
From: Definitely Not Bob <[email protected]>
To: Probably Not Alice <[email protected]>
Date: Mon, 12 June 2017 16:02:43 -0500
Subject: Super Secret EMAIL! Don't let Eve see!
-----BEGIN PGP MESSAGE-----
...
-----END PGP MESSAGE-----
.
QUIT
Thereby leaking at minimum the sender and recipient, as well as any intermediate hosts that relayed the email. Depending on how your MTA handles email, you can also leak subject and other metadata.If your goal is to avoid the lock-in to a particular IaaS vendor while avoiding ops overhead, your better bet is to go up-stack and lock yourself into either Cloud Foundry or OpenShift. At least then you'll be able to migrate from IaaS to IaaS semi-transparently, but you are locking into a platform.
movq $0x2000004, %rax ; // BSD syscalls are divided into classes.
movq $1, %rdi ; // 64-bit registers use %rdi instead of %ebx
lea message(%rip), %rsi; // Relative Address of message
movq $13, %rdx ; // Same Length
syscall ; // x86-64 ASM syscall
movq $0x2000001, %rax ; // Exit Syscall
movq $0, %rdi;
syscall
message: .ascii "Hello World!\n";
[ my public key: https://keybase.io/0x44; my proof: https://keybase.io/0x44/sigs/qbb3tgOe9CDLzBOcneqiqaiNEyWEQ_8UAdGV3ZIBcEY ]