Jump to content

Stagg54

Members
  • Content Count

    104
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Stagg54

  1. Any list we put together is probably still going to have false positives. All we can really hope for is to flag things for further review. It could point out some problems. For instance, a math library that is using TCP/IP is probably an instant red flag. Also any list if we make it public, will just result in a cat and mouse game, because people who are determined will find ways around it. All we are really doing is just making it harder and picking off the low hanging fruit. That is all cyber security in general is doing. A determined and skilled attacker with sufficient resources
  2. So we had a discussion during Virtual Coffee about malicious packages and vetting. How do we verify that code is not malicious? What might flag something as malicious? We can use VI analyzer to check for certain things such as: PW protected VIs Removed BDs Call Library Node .NET nodes Network nodes (TCP, UDP, etc) File I/O nodes Shell commands Run on open Subvis with no icon or hidden under other objects What should we add to that list? Also we need to be careful with the fact that people can use #vian_ignore to
  3. unfortunately I had inherited a giant project. The main VI had a 17 frame deep stacked sequence structure. Frame 17 was the main logic but it needed 16 frames to initialize all the global variables in the correct order. It was written in LabVIEW 5 and upgraded to 6.1 with no SCC. It was my introduction to all things LabVIEW. It was a fun project.
  4. also why did they take the bite out of the upper left corner of the N? It looks weird. Maybe just to help differentiate from the garbage company?
  5. It could use a dose of any kinda color over that boring dull gray.
  6. You must have missed out on the joy of insane objects. https://labviewwiki.org/wiki/Insane_Objects
  7. For all the complaints I have about NXG, that decision I do agree with.
  8. One Word: Scripting Until we have scripting how do they expect anyone to be productive. It's like going back to the dark ages.
  9. We are still looking for more presentations. If you have something please submit it thanks.
  10. As a package creator I would like to be able to see how many people have downloaded my package.
  11. As a package consumer I would like to be able to subscribe to packages so that I get notified when a new version is available.
  12. As a company that uses LabVIEW and has it's own existing internal repository for reuse code, I would like a way for my developers to discover packages in G Central and in our private reuse repository, all from a single portal.
  13. As a community member and package consumer I want to support your efforts.
  14. As some of you may know, we have in the past had an annual CLD Conference in Denver, sponsored by NI. This year it got cancelled and we have been discussing alternatives. After seeing the success of GDevCon, I'm considering bringing something similar to Denver in the next year or so. I'm trying to gauge interest and start some planning. If you could take the time to fill out a short survey, I would greatly appreciate it. https://goo.gl/forms/miafw207AeRAvUxZ2 Sam
  15. Posting your scripting code, so we can exactly what you are trying to do would be helpful. What you are trying to do should be possible. Not sure if there are some limitations way back in 2012. One thing to check would be: Do you save the class before trying to add it to your project? Edited to add: Since the connection between a member vi and a library is a 2 way connection, make sure you save both. I belive a Save All This Library.vi should handle that (it's in the hidden gems pallette if you have it installed, if not its buried somewhere in vi lib).
  16. oh and if your tools need to know what directory things are checked out into, you can always add it to the tools menu. Make them invoke it with the project open and then can pull the items you need out of the project or just use the current project path and compute everything relative to that.
  17. If you do this for external dependencies and everything internal to the project uses a relative path, then your coworkers should be able to check it out to whatever directory they want and not have any issues.
  18. Benoit's suggestion is spot on. That's what I've always done and never had a problem. And you never have to remember to include the vi in your build or mess with any build settings.
  19. I was going to ask, but I guess that answers my question.
  20. FYI, the Peter Bokor one crashes a few minutes from the end. The slider says it 1:05, but it crashes around 1:02.
  21. There is a way to get git to treat specific extensions (and possibly specific files) as binary and not try to merge them... Google the .gitattributes file. It's similar to the .gitignore file and I think it will do what you want.
  22. That is what I typically use... Generally I wrap in a class.
  23. You could call it the jenga or house of cards solution... It works, but if you want to make changes, you better be careful!!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.