license-key | Protect your program with keys to sell | Cryptography library

You have to destroy the accordion before changing the data inside, the best timing to do this is when closing the dialog:

The problem could be with Salesforce Locker Service. Locker service restricts the scope of DOM navigation and manipulation allowed by components.

Debugging the script we found that the isVisible(elem) function was trying to navigate all the way up to the top level HTML node (which was blocked by the Locker Service). The answer at https://forum.handsontable.com/t/handsontable-within-the-salesforce-locker-service/1014 helped in fixing this.

We updated the the isVisible(elem) function as below:

Change next = next.parentNode; to

What you are doing is attempting to authenticate the computer using some data/knowledge that only it has (its MAC and licence key). This is easy to get around as an unlicensed computer can spoof the data and fool you into thinking the request is coming from an licensed computer. If you only transmit the license/MAC data then its possible for any other computer with the knowledge to also impersonate a licensed computer just by intercepting a single request - all the info required to impersonate is contained within the request.

You can't enforce uniqueness of a computer without specialised hardware. This usually takes the form of a dedicated microchip that contains a key or certificate. The data cannot be read from the chip, but the chip can be used to create a digital signature.

Without dedicated hardware the best you can do is to use a unique license key per computer and require all requests to be signed using this key. This relies on the key being private (the signature is sent with the message, not the key itself) and is no guarantee as you don't control the client computer.

Edit - How this works:
Issue a license key to each client. On your server, record each key you issue against the MAC address of the computer it is assigned to. You should probably collect the MAC address at the time of issuing the licence. Do not get clients to 'register' their license. Clients must use the key to sign each request they send and include the signature and MAC in each request. At the server you validate each incoming request by looking up the key using the MAC address and recreating the signature yourself. If the signature matches the one supplied by the client then you know its genuine. Remember - this is still not foolproof! I can buy one license from you and install it on any number of computers so long as I get them all to fake the approved MAC address. I can also give my key to my friends and have them fake the MAC address too.

1. If your function is on Consumption plan, set WEBSITE_MAX_DYNAMIC_APPLICATION_SCALE_OUT to 1 in Application settings.

2. Check your Azure Function runtime version in portal(Platform features> Function app settings). If it's ~2, we need to modify service bus setting in host.json as below.

You could click Vuforia tab on the menu, then click Configuration. Please refer to http://i.imgur.com/ruc9JHB.png

You're using BrokeredMessage (old Azure Service Bus client for .NET, WindowsAzure.ServiceBus). When message is sent as memory stream, it has to be received and deserialized using the same approach. GetBody will work if you construct BrokeredMessage passing in an object of type T.

Note: the next generation client (Microsoft.Azure.ServiceBus) only works raw with byte array (memory stream for the old client). If this is a new project, recommend to stick with that approach rather than serialized types. More info is available in a GitHub issue here.

It's precisely what the error message says, that /data/stardog does not exist. The instructions assume you have an existing location where you want the home directory to be, Stardog does not create it. So you should either create that directory, or open a new terminal, don't do the first command, and change the second to cp stardog-license-key.bin . That will make Stardog's home directory your current directory, specifically, the root of the binary distribution.

I've learned that ed25519 is based on schnorr, at least from what I have read. Finding implementation for the ed25519 was not too hard. I've found the libsodium.net that uses the libsodium (a c++ lib), which wraps the c++ library.

There is also something called NaCl.Net (salt.net) which is a completely managed version of the libsodium.net. The documentation of the NaCl.Net is missing, and things are not working as I expect (The API is different from the one in the libsodium.Net).

Anyhow, with the libsodium.Net I managed to encrypt a small message and get a small encrypted message.

For example, for a 4 bytes message, I get a 20 bytes of encrypted messages. For an 8 bytes message, I get a 24 bytes message.

The extra 16 bytes are not bad at all (the key size is 32 bytes, which mean 256Bits, which in this algorythm should be good)

Algorithm details

Key exchange: Curve25519 Encryption: XSalsa20 stream cipher Authentication: Poly1305 MAC

Signing the message creates a larger signed message, but I don't need it. I'm going to calculate a hash for the data, and generate a key from it (using the encryption).

When the key is received, it's being decrypted, and the given hash is then being compared to the hash that was calculated on the machine.

The answer here turns out to be that you must run ensure-transactor from the root director of the datomic package. This is apparently true for most of (but not all) datomic scripts. It seems to pertain in particular to one-off scripts like ensure-transactor that you'd run once.