If you are new to OAuth2, please read the Introduction to OAuth 2.0 and OpenID Connect first.
This section defines a glossary, provides additional information on OpenID Connect and introduces OAuth 2.0 Clients.
If you are new to OAuth2, please read the Introduction to OAuth 2.0 and OpenID Connect first.
This section defines a glossary, provides additional information on OpenID Connect and introduces OAuth 2.0 Clients.
I had a heck of a time getting a Cuckoo sandbox running, and below I hope to help you get one up and running relatively quickly by detailing out the steps and gotchas I stumbled across along the way. I mention this in the references at the end of this gist, but what you see here is heavily influenced by this article from Nviso
While building a React Chrome extension using the create-react-app utility (v2.x), I came across the following error on loading my unpacked extension:
Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘self’
blob: filesystem: chrome-extension-resource:”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-
GgRxrVOKNdB4LrRsVPDSbzvfdV4UqglmviH9GoBJ5jk=’), or a nonce (‘nonce-…’) is required to enable inline execution.
Basically, this error arises as Chrome (or almost any modern browser) will not allow inline scripts to get executed. This CSP restriction resulted in the above error as the build script in create-react-app bundles the .js files in <script> tags in the <body> of index.html.
| // code courtesy of Toby team | |
| chrome.storage.local.get("state", o => ( | |
| ((f, t) => { | |
| let e = document.createElement("a"); | |
| e.setAttribute("href", `data:text/plain;charset=utf-8,${encodeURIComponent(t)}`); | |
| e.setAttribute("download", f); | |
| e.click(); | |
| })(`TobyBackup${Date.now()}.json`, o.state) | |
| )); |
Note: this is a work-in-progress and will be updated with more information over the next few days.
This guide will walk you through deploying your own instance of the open-source Parse Server. This would be a good starting point for testing your existing application to see if the functionality provided by the server is enough for your application, and to potentially plan your migration off the Parse Platform.
This guide will walk you through using Elastic Beanstalk (EB), which is an AWS service similar to Heroku. Why use EB rather than Heroku? Elastic Beanstalk does not lock you into Heroku-specific ways of doing things, is likely cheaper to run your backend on than Heroku, and it integrates with other services that AWS offer (and they offer almost everything one needs to run an application these days).
press F12 on the Dell startup screen
Instructions are here: https://www.ubuntu.com/download/desktop
| #!/usr/bin/env sh | |
| #i tried it and working like charm just have to note make the file .sh chmod +x and you may need sudo to run with permission but be carefull with sudo | |
| #be sure the $JAVA_HOME is configure correctly or make it static as commentedline 7 below | |
| OLDDIR="$PWD" | |
| if [ -z "$CACERTS_FILE" ]; then | |
| # you should have java home configure to point for example /usr/lib/jvm/default-java/jre/lib/security/cacerts | |
| CACERTS_FILE=$JAVA_HOME/jre/lib/security/cacerts | |
| fi |
| packages: | |
| yum: | |
| git: [] | |
| gcc: [] | |
| make: [] | |
| openssl-devel: [] | |
| ImageMagick: [] | |
| option_settings: | |
| - option_name: NODE_ENV |
Bucket policy is an access policy available for you to grant anonymous permissions to your Minio resources. Bucket policy uses JSON-based access policy language.
This section presents a few examples of typical use cases for bucket policies. The policies use testbucket strings in the resource value. To test these policies, you need to replace these strings with your bucket name. For more information please read Amazon S3 access policy language
The following example policy grants the s3:GetObject permission to any public anonymous users. This permission allows anyone to read the object data under testbucket, which is useful for when you have publicly readable assets. A typical example is a website assets stored in testbucket.
$ ./zenbot.sh trade gdax.eth-USD --trend_ema 20 -period 7m --max_slippage_pct 0.48 --poll_trades 6000 --order_poll_time 6000 --order_adjust_time 6000 --oversold_rsi_periods=1000 --oversold_rsi=1000 --rsi_periods=1100 --neutral_rate=0.1 --max_sell_loss_pct=0.85 --max_buy_loss_pct=5 --buy_pct=100 --sell_pct=100 --selector gdax.eth-usd --markup_sell_pct 0.25 --markdown_buy_pct 0.00 --reset-profit