#Privacy on datacrow update#
#Privacy on datacrow code#
#Privacy on datacrow windows#

This guide will help you understand what is data privacy and it's importance.ĭata privacy is part of the data protection area that focuses on compliance with data privacy regulations by dealing with the proper handling of privacy and the expectation of privacy by the public. Your Data Crow installation will then execute the actual query to the 3rd party service.In this digital age, accessing to information has been made easy which now puts a gray line to our privacy. This service will add the (my) API key, signing your request. To overcome this issue I will implement a small server to which you send your initial request. Given that Data Crow open source I currently only have the choice to put the key in the code, somewhere. This key is then unique to the product and should not be shared. Many online services provide a developer with a single key. After that I will move on to Discogs for audio.Īdditionally I will implement a simple Data Crow service to sign requests. I have implemented a first version of MobyGames (excellent for english information on games) which I'll continue to test and update. Many of the old ones had to be removed as they either no longer existed, did become paid services or their structure had been changed completely. read moreĬurrently I am working on version 4.4. This is also reported as the solution of the issue we are currently facing. This ensures that the executables you get with Data Crow are created by me - as I have signed it using my certificate. The latter is bit of an advanced way where you need to buy a certificate from an organization which you use to sign the executables you generate for your product. I now have two options, either I downgrade to Java 11 (from Java 17) so that I can downgrade Launch4j (the old version did not have this issue), or, I take steps to digitally sign the executables. After doing additional research it turns out that multiple virus scanner can flag executables generated by Launch4j (which I used) as a virus, where actually there's no virus present a false positive. I always scan my own environment and there are no viruses on my build machine. The new executables are marked by some virus scanners as a virus / threat. The reason is an issue introduced when the library was updated which generates the executables for Data Crow. I am currently working on a small release.

Added an executable for the server version. Updated the completely outdated About dialog contents. Discogs maximum search results has been increased (online services pack version 1.4). The main application icon now consists of multiple sizes to allow support for multiple displaying purposes. Always go to the HTTPS version in the browser when navigating to the web module from now on. If the application needs to be running in a web environment it is recommended to add a valid certificate which can be configured in ssl/datacrow-ssl.properties.

This can be used for internal / local network use. A default self signed certificate has been added. The web modules is now configured for HTTPS (only). All other developers won't be able to do is to generate the official Data Crow executables.

#Privacy on datacrow code#

There is no code hidden from you, it's still true to form for an open source project. This will only work on my build machines as the certificate is private to myself.

#Privacy on datacrow update#

I had to update the datacrow-install module to include the signing.

#Privacy on datacrow windows#

This means no more issues with virus scanners and no more unknown publisher messages for Windows users. The executables of Data Crow are now signed by my own official certificate.