Running the example:
base_url=https://gitlab.your-host client_secret=$client_secret client
_id=$client_id port=8081 go run main.go
2018/10/10 12:57:57 Using port: 8081
Running the example:
base_url=https://gitlab.your-host client_secret=$client_secret client
_id=$client_id port=8081 go run main.go
2018/10/10 12:57:57 Using port: 8081
// recieve message | |
// event object contains: | |
// - data: message sent | |
// - origin (host from which the message was sent, e.g. http://blah.example.com) | |
// - source (reference to a Window object from which message was sent) | |
function postMessageHandler( event ) { | |
console.log("We've got a message!"); | |
console.log("* Message:", event.data); | |
console.log("* Origin:", event.origin); | |
console.log("* Source:", event.source); |
{"lastUpload":"2020-07-23T20:28:37.984Z","extensionVersion":"v3.4.3"} |
My Elasticsearch cheatsheet with example usage via rest api (still a work-in-progress)
Shared memory is an efficient means of passing data between programs. Because two or more processes can use the same memory space, it has been discovered that, since shared memory is, by default, mounted as read/write
, the /run/shm
space can be easily exploited.
That translates to a weakened state of security.
If you’re unaware, shared memory can be used in an attack against a running service. Because of this, you’ll want to secure that portion of system memory.