Can't build freetaxii.go

[kripskroll]

Hi all,

Probably my poor knowledge with go, but I can't succeed to build freetaxii.
Here is the error I have (extract only one)
package github.com/freetaxii/libstix2/resources/collections: cannot find package "github.com/freetaxii/libstix2/resources/collections" in any of:
/usr/local/go/src/github.com/freetaxii/libstix2/resources/collections (from $GOROOT)
/root/myGOProjects/src/github.com/freetaxii/libstix2/resources/collections (from $GOPATH)

If I go to the folder /root/myGOProjects/src/github.com/freetaxii/libstix2/resources then I have only these files/folder :
doc.go helpers resources.go

Thanks in advance for your kind help

--Kripskroll

[jordan2175]

Thanks for the reminder. I have been updating the libstix2 package to support 2.1 and have not yet updated the TAXII Server code to work with it. I will try and get that done.

[kripskroll]

Thanks Jordan,I was thinking I was doing mistakes. May I ask you why, if i'm doing a Discovery from a client, it does not work and I can't have the available collections.I'm just using the python libraries from MITRE (cti-taxii-client) with their sample easy code (https://www.mitre.org/capabilities/cybersecurity/overview/cybersecurity-blog/attck%E2%84%A2-content-available-in-stix%E2%84%A2-20-via)I achieved to workaround the certificate issue to not verify it but now I receive a "406 Client Error: Not Acceptable for url: https://10.10.10.232:8000/taxii2/"The FreeRadius Server log is showing me that I'm doing a Discovery : 2020/03/20 00:12:50 INFO: Found Discovery request from 10.10.10.232:46640 at /taxii2/ Thanks in advance. Do not hesitate to tell me to ask through github bug interface if needed and you think that is useful All the best in this weird period. --Kripskroll Le jeudi 19 mars 2020 à 18:31:13 UTC+1, jordan2175 <[email protected]> a écrit : Thanks for the reminder. I have been updating the libstix2 package to support 2.1 and have not yet updated the TAXII Server code to work with it. I will try and get that done. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.