![]() ![]() Select your desired file type and download your QR code right to your device. ![]() Create your QR code and customize the style and color. Don't try to encrypt the QR code itself (not sure that terminology actually makes any sense) but instead, compress and encrypt your data, then QR-encode the resulting encrypted data. Choose a URL and paste it into the generator. If you can find compression and encryption algorithms that work for both you & your client (and a safe way to distribute keys and so on), then I don't think it's particularly hard to satisfy your original request. If the message is much smaller than this limit, then you won't care about this (could use the highly-bloating PGP for example). If the message you're transmitting is close to this limit, you'll want to choose a crypto algorithm that has output size equal to input size (AES is one example). QR code blocks have a limited capacity of 2953 bytes of 8-bits each. However one of the implications is especially relevant to QR codes - how much the crypto step bloats your message. If you're not sure or the approach needs to be general (work for different choices of crypto algorithm) you can always compress it's safe, just sometimes pointless.Ĭhoice of crypto algorithm has many implications (key management etc. It isn't always needed as a separate step, because some crypto algorithms perform compression for you - for example, PGP compresses data before encrypting. Ĭompressing before encrypting is a best practice. Note well, crypto is non-obvious, approach with respect & caution, don't just slam something together. In which your primary challenge is to choose compression & crypto algorithms that suit your purposes. > (QR encode) -> QR of encrypted compressed messageĮncrypted compressed message <- (QR decode) <. > (encrypt) -> encrypted compressed message The obvious approach (hi-level) looks like this message If that's true - if for some reason you have to transmit the actual data through a non-internet channel, and the actual data has to be wrapped in a QR code format, then there's a different way to do this. for bills or payment data where that could be happening. That's not the most usual use case - not what most of the respondents on this forum would naturally consider - but I can imagine some realistic use cases e.g. However, I'll infer from your original question that the channel you're using is analog (paper?), or digital but not internet-connected (digital photos of a paper original or screen shot, or ?). As Tadmas pointed out, QR is just an encoding. and if it does make sense, you don't need a QR code at all, just send the URL. If the channel you're using to communicate with your client is digital and internet-connected, maybe that makes sense. Other answers suggest you could use the QR code to encode a URL, and then ensure the service at that URL provides the authentication / security you need. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |