I hereby claim:
- I am sykesm on github.
- I am sykesm (https://keybase.io/sykesm) on keybase.
- I have a public key whose fingerprint is 4884 F32E 7A73 3714 3FCA 540D BDBE CC3A C6E8 562A
To claim this, I am signing this object:
echo $(curl -s http://www.dinopass.com/password/strong)-$(curl -s http://www.dinopass.com/password/strong) |
package main | |
import ( | |
"fmt" | |
"io/ioutil" | |
"os" | |
"os/exec" | |
"runtime" | |
"github.com/cloudfoundry-incubator/ducati-daemon/lib/namespace" |
#!/usr/bin/perl | |
use NetAddr::IP; | |
use POSIX qw(strftime); | |
my $dnsmasq_leases_path = '/var/run/dnsmasq-dhcp.leases'; | |
my $dhcpd_leases_path = '/var/run/dhcpd.leases'; | |
my $network_names_path = '/opt/vyatta/config/active/service/dhcp-server/shared-network-name'; | |
my %networks_by_subnet; |
I hereby claim:
To claim this, I am signing this object:
@font-face { | |
font-family: "Inconsolata-dz for Powerline"; | |
font-style: normal; | |
font-weight: normal; | |
src: url(data:font/opentype;charset-utf-8;base64,T1RUTwALAIAAAwAwQ0ZGIFWjzGQAAAo0AABX1kZGVE1bUJ1iAABkjAAAABxHREVGAVoABAAAYgwAAAAgT1MvMl4Wx0gAAAEgAAAAYGNtYXD6yx74AAAGnAAAA3ZoZWFk/OhPcgAAALwAAAA2aGhlYQboAW4AAAD0AAAAJGhtdHg1ZDKaAABiLAAAAl5tYXhwAS1QAAAAARgAAAAGbmFtZUgkeAsAAAGAAAAFHHBvc3T/hgAzAAAKFAAAACAAAQAAAAECjz7UcWpfDzz1AAsD6AAAAADNuYSFAAAAAM25hIX/4P8tAnYDxwAAAAgAAgAAAAAAAAABAAADx/8zAMgCV//g/+ECdgABAAAAAAAAAAAAAAAAAAAAAgAAUAABLQAAAAMCVwH0AAUACAKKArwAAACMAooCvAAAAeAAMQECAAACCwYJAwADAAAAgAAALwAAAWsAAAAAAAAAAFBmRWQAQAAg4LMDNP9MAAADxwDNAAAAEwAAAAACEQLSACAAIAABAAAAEgDeAAEAAAAAAAAAmwE4AAEAAAAAAAEAHAIOAAEAAAAAAAIAAgIxAAEAAAAAAAMAKgKKAAEAAAAAAAQAHALvAAEAAAAAAAUAEAMuAAEAAAAAAAYAGgN1AAEAAAAAABAAHAPKAAEAAAAAABIAHAQhAAMAAQQJAAABNgAAAAMAAQQJAAEAOAHUAAMAAQQJAAIABAIrAAMAAQQJAAMAVAI0AAMAAQQJAAQAOAK1AAMAAQQJAAUAIAMMAAMAAQQJAAYANAM/AAMAAQQJABAAOAOQAAMAAQQJABIAOAPnAEMAcgBlAGEAdABlAGQAIABiAHkAIABSAGEAcABoACAATABlAHYAaQBlAG4AIAB1AHMA |
#!/bin/bash -ex | |
pwd | |
# /Users/cfdojo/workspace/fabric/standalone | |
killall orderer peer | |
rm -rf output peer1 peer2 | |
mkdir -p output/crypto | |
cryptogen generate --config testdata/crypto-config.yaml --output output/crypto |
/* | |
Copyright IBM Corp. All Rights Reserved. | |
SPDX-License-Identifier: Apache-2.0 | |
*/ | |
package simple | |
import ( | |
"fmt" |
/* | |
Copyright IBM Corp. All Rights Reserved. | |
SPDX-License-Identifier: Apache-2.0 | |
*/ | |
package factory | |
import ( | |
"errors" |
Our current chaincode deployment model looks a lot like a PaaS; chaincode developers write code in the language of their choice and push it to the peer for execution. The peer, on demand, transforms the code into an executable package, launches the chaincode in an execution environment, and routes requests to the running chaincode.
Unfortunately, we have implemented this by hard coding the logic for packaging, building, and running chaincode inside Docker containers. In addition to making it difficult to experiment with new chaincode types, the implementation requires operators to grant the peer access to a Docker daemon. Since Docker daemon access enables the peer to perform a number of privileged actions, it's strongly discouraged in security conscious environments. This binding also prevents operators
External Chaincode Launcher | |
Roadmap | |
Matthew Sykes | |
IBM | |
[email protected] | |
* Why? |