Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CryptoHelper writing to >dev>null causes problems on Windows server #15

Closed
ClausScherschel opened this issue Jul 10, 2020 · 3 comments
Closed

Comments

@ClausScherschel
Copy link

@tiamo Hey there and my apologies for bothering you again.
Telling from your examples, it seems your library is based upon Sebastien Malot's AS2Secure. I'm trying to rewrite our AS2 service which uses AS2Secure.
The CryptoHelper components delegates the result of pkcs7 verification to >dev>null which works on Unix but not on a Windows machine. On Windows it needs to be >nul. AS2Secure had the same problem; I did change this in that library directly because otherwise, we couldn't get a message through.
Though PHP gives only a warning level error, it might be the reason, why the message cannot be further processed, it stops dead stating "Signature Verification Failed". The response MDN seems to be empty; client says there is no MDN report.
Maybe there's a chance of having a configure option for this, if not auto-detecting environment.

@tiamo
Copy link
Owner

tiamo commented Jul 10, 2020

Fixed in v1.4.4

@ClausScherschel
Copy link
Author

Awesome! I appreciate your enthusiam, effort, and good work, Vladyslav!

@tiamo
Copy link
Owner

tiamo commented Jul 10, 2020

Thanks!

@tiamo tiamo closed this as completed Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants