Leaderboard

Name: Encryption Submitter: Ton Plomp Submitted: 07 Sep 2011 Category: *Uncertified* LabVIEW Version: 2010 License Type: BSD (Most common) This package consist of a series of tools in native LabVIEW 2010 code. For encryption/decription the AES (Rijndael) routine is used with key sizes of 128, 192 and 256 bytes. The encryption supports the following block modes: EBC CBC CFB128 OFB For signing of string/packages it performs the SHA-1 and SHA-2 hashing, for MD5 hashing the OpenG functionality is used. The hash functions return a binary string and a hex-formatted string with the hash. The following hashes are supported: MD5 (via OpenG library) SHA1 SHA-2 224 bit SHA-2 256 bit SHA-2 384 bit SHA-2 512 bit For Hashed key authentication the HMAC functionality is provided based on the supported hash functions. The used functions are tested against NIST public test vectors. The use of these functions is not: secure the code does not try to protect it's memory nor the used keys. © Ton Plomp 2011 - No warranty implied. Click here to download this file

You just need to liberally use "Create SubVI" in logical places. I'm generally pretty anal-retentive about the 1 screen BD rule. However, I have one vi that is such a humongous mass of spaghetti code I'm too embarrased to post it. It's about 6 screens. It already has almost 100 subvis and still needs more. At this point I'm looking at just rewriting the whole thing. If something gets that messy visually, there's a good chance it's messy logically, too.

This is offtopic, sorry, but all I could think when I read OP was "How is babby formed?"

Almost all of my apps are state machines within state machines. Take a look at these two galleries on the dark-side to get some ideas. http://forums.ni.com/t5/media/gallerypage/user-id/9539/album-id/9000 http://forums.ni.com/t5/media/gallerypage/user-id/9539/album-id/9006 Ben