Interesting presentation about Hashgraph and how it solves the distributed consensus issues
Great video explaining differences between NEO and Ethereum:
Interesting thread on Reddit about Decentralized Exchanges as I think Exchanges now are one of the weak link in the cryptocurrency ecosystem.
Some are slow and lack support, others are extra regulated or conversely not regulated and prone to be scam or unstable or unsecure.
I generally tend to dislike anything that grows too big and centralizes everything in one place, being that a physical place (lack of redundancy) or a company or a controlling group of people … all these are “Single Points of Failure” in different ways …
Cardano could be doing very good in the future, and now it is still very cheap to get in! 😄 🎉
This is a great interview with Charles Hoskinson with a lot of details about it:
it seems the project is super well thought by peer reviewed academics with great roots and credibility, Charles Hoskinson was one of the founders of Ethereum … probably good to think for long term gains on Cardano being it still “ahead its time”, some say could reach $1 in 2018 which would be a 10x from where we are now … (this is not financial advice LOL 😉 )
3rd gen cryptos are all about 3 topics:
This is a quick note that may save you some painful debugging (wrote on Nov 2017)
Straight to the solution:
If you are trying to run a Dockerized version of Security Monkey, when you build the Docker Containers remember to COMPLETELY REMOVE the AWS credentials variables from secmonkey.env because if you leave those variable in the file defined as empty, they will be passed empty into the container and this will prevent boto3 to escalate and try SecurityMonkeyInstanceProfile.
So build those containers with the secmonkey.env file without any reference to AWS credentials:
root@secmonkeyhost:~/security_monkey# grep AWS secmonkey.env root@secmonkeyhost:~/security_monkey#
In the example above grep correctly returns empty, unless of course you have other stuff in there not related to aws auth.
The context in detail:
I deployed sec monkey on 2 AWS EC2 instances, they are identical in all respects, one instance is running Sec Monkey installed manually, and everything works, the second instance is running Sec Monkey Dockerized version and I get the AssumeRole error in the logs.
Both instances return the same when I run:
aws sts assume-role --role-arn "arn:aws:iam::XXXXobfuscatedXXXX:role/SecurityMonkey" --role-session-name "dev"this is the error:
secmonkey-scheduler | ClientError: An error occurred (InvalidClientTokenId) when calling the AssumeRole operation: The security token included in the request is invalid.
AWS metadata is available via curl inside the containers:
This comment has been added as a pull request onSecurity Monkey Github: