Comments (4)
Thanks for your bug report. I have the same problem, although for me it seems to be a warning only. I have spent a frustrating hour trying to track it down with no luck. The bug you referenced and corresponding xmlsec change looks promising, but I'm not really sure what to do about it. Thoughts?
from go-xmlsec.
Hmm, I guess somehow I missed the word "warning". I should check to see if it actually works and I'm just an idiot. There's another set of bindings for xmlsec, lestrrat/go-xmlsec, which also produces these warnings, so maybe it's not that big of a deal.
The first "solution" that comes to mind is to vendor in that modified xmlsec library, and modify the cgo directives to instead include the modified version, but that working depends on if xmlsec can be statically linked. (I think just xmlsec being static would work, since its dependencies shouldn't care about the modification.)
Are there any other libraries that do something similar to this one? I guess my focus is to get saml working, but having a library that doesn't spit out a bunch of nasty warnings is always nice too.
from go-xmlsec.
Yeah, it builds okay, I just didn't know it. Now your saml library gives me expected element type <EntityDescriptor> but have <EntitiesDescriptor>
when it's trying to load the provider data from testshib, but I should probably file that issue over in the other repo.
from go-xmlsec.
I (finally!) figured out the correct voodoo in [760a575] to silence the warnings on darwin/clang and linux/gcc.
from go-xmlsec.
Related Issues (17)
- xmlenc: add support for additional ciphers & algorithms HOT 1
- add support for encryption HOT 1
- consider implementing xmlenc with libxmlsec rather than native HOT 1
- configure libxmlsec to not spew stuff to stdout HOT 2
- audit our use of unsafe.Pointer and C.CString to make sure we're not leaking memory HOT 1
- add test cases for XML encryption
- dont pollute the libxmlsec/libxml2 global state with error handlers HOT 1
- Missing LICENSE information
- Reference URI HOT 1
- Verify, xmlsec1 says 'OK', but go-xmlsec/examples says 'signature is not correct'
- Race condition HOT 2
- fix linux CGO flags for go 1.10 HOT 3
- can not build HOT 2
- How to install this library for windows HOT 1
- Can not build with GOARCH=arm64
- FreeBSD
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-xmlsec.