Open ZGY issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues2024-03-16T21:01:30Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues/1golang binding2024-03-16T21:01:30ZJackie Ligolang bindingHi,
I'm Jackie from Target Energy Solutions. We have a golang binding for the ZGY library. Do you mind us contributing to this repo?
Best RegardsHi,
I'm Jackie from Target Energy Solutions. We have a golang binding for the ZGY library. Do you mind us contributing to this repo?
Best Regardshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues/18.NET bindings2021-06-24T10:14:51ZRobert Schmidt.NET bindingsWe ([Cegal](https://cegal.com/)) have a branch with basic C and .NET bindings to the (new) OpenZGY API.
- netstandard2.0, with xunit tests and a console app for net5.0
- Capable of building Debug and Release nuget packages
- Console app...We ([Cegal](https://cegal.com/)) have a branch with basic C and .NET bindings to the (new) OpenZGY API.
- netstandard2.0, with xunit tests and a console app for net5.0
- Capable of building Debug and Release nuget packages
- Console app can dump ZGY meta data, copy and compare ZGY content
- Windows only for now (I would need assistance for Linux support)
- Seismic Store support - sdapi binaries and headers are added to branch
- 2 source files are added to OpenZGY.vcxproj to provide the C bindings, no changes to existing code
- Bindings expose a simplified API for now (e.g. no compression or const support)
Would this be of interest for this repo?
Until more complete, it should probably live as a separate branch.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues/25implications associated with Python(pickle) module.2022-12-30T09:03:08ZJayesh Bagulimplications associated with Python(pickle) module.I am working on a vulnerability issue of the Pickle module in open-zgy.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/security/vulnerabilities/18266
The pickle library’s documentation discour...I am working on a vulnerability issue of the Pickle module in open-zgy.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/security/vulnerabilities/18266
The pickle library’s documentation discourages the unpickling of untrusted data. Currently, deserialization is happening with a simple approach.
To prevent unsafe deserialization there are multiple approaches are there.
1) Implementing a message authentication code (MAC) to ensure the data integrity of the payload. (hmac and hashlib)
2) Run the deserialization code with limited access permissions.
3) Validate Inputs.
I would like to hear which will best suit it as well as compatibility option for all existing things.
CC: @Srinivasan_Narayanan @nursheikh @chadJayesh BagulJayesh Bagulhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues/28Please update OpenVDS dependencies in dll-hell.md2023-05-04T14:03:12ZJørgen Lindjorgen.lind@3lc.aiPlease update OpenVDS dependencies in dll-hell.mdVersion 3.2 and newer of OpenVDS does not have any visible dependencies, except sytem libraries such as:
- linux-vdso.so.1
- libpthread.so.0
- libdl.so.2
- libstdc++.so.6
- libm.so.6
- libgcc_s.so.1
- libc.so.6
- ld-linux-x86-64.so.2
T...Version 3.2 and newer of OpenVDS does not have any visible dependencies, except sytem libraries such as:
- linux-vdso.so.1
- libpthread.so.0
- libdl.so.2
- libstdc++.so.6
- libm.so.6
- libgcc_s.so.1
- libc.so.6
- ld-linux-x86-64.so.2
The situation is very similar on Windows. Therefor the mentioning of OpenVDS in the dll-hell section is outdated and should be revised.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-zgy/-/issues/30reading zgy directly from cloud2023-12-27T10:09:52ZQiang Fureading zgy directly from cloudAny example to read zgy files on cloud from providers by the OpenZGY if it is supported?Any example to read zgy files on cloud from providers by the OpenZGY if it is supported?