git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
git clone https://gist.github.com/dd6f95398c1bdc9f1038.git vault
cd vault
docker-compose up -d
export VAULT_ADDR=http://192.168.99.100:8200
Initializing a vault:
vault init
Note: I've only briefly read the related CPI paper (PDF), this is just initial impressions after playing around with it a bit.
All the code and binaries I used can be downloaded here. Note that I removed -DFORTIFY_SOURCE=2
to make the examples a bit simpler.
-fsanitize=safe-stack
basically seems to move stack based buffers off the actual stack, onto another segment of memory (I'll call it the fake stack). The actual stack then stores references to this segment. For example:
char buf[20];
printf("%p\n", buf);
/* | |
* Demonstrates that an RSA signature does not uniquely identify a public key. | |
* Given a signature, s, and a message m, it's possible to construct a new RSA key | |
* pair such that s is a valid signature for m under the new key pair. | |
* | |
* Requires Go version >= 1.5. Go <= 1.4 doesn't work due to a bug in the bignum | |
* package: https://github.com/golang/go/issues/9826 | |
* | |
* Written in 2015 by Andrew Ayer <[email protected]> | |
* |
mainmem.backing = "swap" # disable swapping | |
MemTrimRate = "0" # disable returning unused memory to the host | |
sched.mem.pshare.enable = "FALSE" # disable page sharing | |
prefvmx.useRecommendedLockedMemSize = "TRUE" # force memory to be pre-allocated on host | |
scsi0.virtualDev = "pvscsi" # fasted disk i/o subsystem (requires driver off pvscsi.flp floppy disk image) | |
scsi0:0.virtualSSD = 1 # if running off an SSD | |
## also, preallocate the VMDK disks |
Chromium OS is cool. Chromium OS with crouton is cooler. Chromium OS with Docker is even cooler. This is specifically a guide for the Chromebook Pixel 2 (2015), but I can't think of any reason it wouldn't work with other devices.
# This program is free software: you can redistribute it and/or modify | |
# it under the terms of the GNU General Public License as published by | |
# the Free Software Foundation, either version 3 of the License, or | |
# (at your option) any later version. | |
# | |
# This program is distributed in the hope that it will be useful, | |
# but WITHOUT ANY WARRANTY; without even the implied warranty of | |
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
# GNU General Public License for more details. | |
# |
"""Ansible dict filters.""" | |
# Make coding more python3-ish | |
from __future__ import (absolute_import, division, print_function) | |
__metaclass__ = type | |
from ansible.errors import AnsibleError | |
#define macros | |
EXE = executable.exe | |
SRC = src | |
BIN = bin | |
INT = obj | |
INCL = include | |
OCV_INC = "$(OPENCV_DIR)\..\..\include" | |
OCV_LIB = "$(OPENCV_DIR)\lib\opencv_world310.lib" |
A DLL can be loaded and executed via Excel by initializing the Excel.Application COM object and passing a DLL to the RegisterXLL method. The DLL path does not need to be local, it can also be a UNC path that points to a remote WebDAV server.
When delivering via WebDAV, it should be noted that the DLL is still written to disk but the dropped file is not the one loaded in to the process. This is the case for any file downloaded via WebDAV, and they are stored at: C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\TfsStore\Tfs_DAV\
.
The RegisterXLL function expects an XLL add-in which is essentially a specially crafted DLL with specific exports. More info on XLL's can be found on MSDN
The XLL can also be executed by double-clicking the .xll file, however there is a security warning. @rxwx has more notes on this here inc