All Activity

It's not listed in https://www.ni.com/en/support/documentation/bugs/24/labview-2024-q3-bug-fixes.html As LabVIEW user I feel happy for their attention to this. As OpenG ZIP developer I feel a bit cheated. 😁

This bug has been fixed by NI in patch 24.3.2f2 of LabVIEW 2024 Q3

I've looking to find the right package/install file to get this capability on computers that don't have LabVIEW Development. I'm building EXE and creating installers, but I want to add this capability so that I can monitor these computers via the browser

We do not have one. We are discussing it...but, unfortunally, we also started collaborating (because we have to...) assuming we will, eventually, and I had to provide the application. The application started as a very basic and incomplete one but in the last weeks it started to became a little bit to "functional and usable" to be honest. Of course, if we will really have a contract I will remove the time-bomb. Thanks! I used dotNET Cryptography Library, a package on VIPM.

You want EVP_PKEY_verify.

Do you have a contract in place with this customer? It sounds like no. If you DO have a contract, then does the contract allow for time-bombs in delivered software?

Just saw this update. Will take a look.

A couple of ideas: Include a license file that clearly explains what they can and cannot do (e.g., no distribution, no use without a valid license, 30 day trial period, etc.) Use a hardware dongle to prevent copies (you can just encrypt the executable, which can then only be started when the dongle is present. No programming required.) If the application is not licensed (e.g., during a 30 day trial period Automatically shutdown the application after 30 minutes Limit the number of data points they can collect (e.g., limit file size to 1 Mib or 100k samples) Turn off certain features (e.g., limit the types of reports that can be produced) Of course, it depends on what value the application represents and how "useful" it is outside your partnership. At some point, however, you will have to trust them enough to not misuse your software outside what is being agreed. If you don't trust them enough to uphold such an agreement, it is probably better not to go into a partnership...

I though about the hack to set the back the clock. I don't know, honestly: the application produce data where the real timestamp tagged with the data is very important. If they will change the clock of the system than everthing is compromised. Yes, it will always be possibile to compensate the offset in the log files or in the stream of data.... I don't want to make it pro hacker proof, I simply want to make inconvenient to keep using it and, most importantly, to go to a third party client and distributed the application forever even if our partnership doesn't go thorough. Regarding your suggested solution: I'm still pushing updates to the application, to solve bugs or add futures. I guess I could put the counter inside the main .ini file, between the entry generated by LabVIEW. Maybe as a second check, just in case they will start to change the system clock... Right now I was trying to generate a license file (with the expiration date), signed with a private key generated with OpenSSL. Now I'm looking for a way to read it using the public key in LabVIEW. Marco.

My 2c: I guess that the problem with an expiration date on an offline computer is that you have no means for the executable to verify that they didn't set the clock backwards to extend indefinitely their usage. If you don't expect them to be pro hackers, what about protection by simple obfuscation? E.g. the incremental time the program has run, saved periodically in obfuscated form in an essential key file, masked as "configuration"? With some mechanism to make more complicate to get through just by rewriting an older file in place of it?

Hi, I'm looking to license an application that will run exclusively on offline systems. I came across the "Third Party Licensing & Activation Toolkit API" available through JKI VIPM, but from what I understand, it requires an online activation process, which wouldn't work for my use case. Are there any other libraries or toolkits you’d recommend? I also checked out Build, License, Track from Studio Bods (link), but I’m not clear on what the free tier offers, or if it's even available. I realize the irony of asking for a free toolkit to license an application! However, I’m not looking to profit from this. I simply want to protect an application that I need to provide to a potential industrial partner while we finalize our collaboration. Unfortunately, I have to hand over the executable, but I want to ensure the application won’t run indefinitely if the partnership doesn't go through. Thanks, Marco.

Shameless self-plug: I do have an online video course on Using Git Effectively. It includes some material on GitLab as well. https://www.sasworkshops.com/using-git-effectively-course-preview

yeah the easy way is just use System Exec to call Git from the CLI. I would also look at these: https://www.vipm.io/package/hse_lib_git_api/ https://www.vipm.io/package/hse_lib_gitlab_api/

I would recommend to use the Bash console commands. If you want some tool support use TortoiseGIT or GitExtension: https://gitextensions.github.io/ https://tortoisegit.org This is also a very good way to learn the GITcommands: (GIT Online-Sandboxtests) https://learngitbranching.js.org/

Yeah it is getting out of hand. Like others have mentioned, I used to browse here daily (often multiple times per day) but since the spam bots took over I stopped coming altogether.

Unfortunately yes. First signed up 50 minutes ago and started spamming about 5 minutes later, then spamming about every 5 minutes. Second signed up 10 minutes ago and just started spamming. Definitely related as it is both about Norton spam. I'm very anti violence but these guys really get the worst in me out! 👿

Back again today, new user related I think

The analog input nodes won't be able to compile in a SCTL regardless of the rate you set. On the inside of the AI node, they need multiple cycles for the low level communication to the ADC chips. Like crossrulz says, the limiting factor is that chip. OP might be able to hit their target with an NI-9223. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Km2SAE&l=en-US

Thank you for your continued reports. If it continues to be a problem Michael will twist various knobs behind the scenes.

Unfortunately it seems not. They said both (the two I checked) that they were created less than an hour ago, when I looked this morning (GMT+2).

Hopefully, these are just those sleeper accounts Michael mentioned earlier.

Guess who's back? Back again? Spammers back. Tell Admin...

Hey everyone, I'm trying to do a similar build/install on a Linux RT device (cRIO-9045), and am also getting error 13, I think it could be for similar reasons as this thread. Since Linux RT isn't Ubuntu based, any idea on how to get libzmq with draft APIs downloaded on there?

Thank you so much for your responses. I haven't tried anything as I am very new to gitlab. I'll look into them and see how it goes. Thank youuu

When you search for a LabVIEW toolkit, you should start on www.vipm.io Take a look at this one : https://www.vipm.io/package/hse_lib_gitlab_api/ if you need support HSE has a discord server, they are quite responsive.