You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
The Connect() function takes filesystem paths to the certificate and private key files. That's too limiting — the server may not have filesystem storage available, or the private key may be considered too sensitive so it might be kept in a Keychain-like store or an LDAP server.
Probably the most flexible way to do this would be for Connect() to take a tls.Certificate as a parameter, and let the caller load the certificate by calling either LoadX509KeyPair or X509KeyPair, the latter of which takes the components as raw byte arrays.
(I just filed the exact same issue as huo-ju/Go-Apns#3. Apologies for copying and pasting the text, but the issue with both packages is identical.)
The text was updated successfully, but these errors were encountered:
I've added apns.NewService in c7ffee5 which allows the caller to pass in a custom tls.Config. This would let you load in your own certificates, override the SSL verification behaviour, etc. For an example, see http://godoc.org/github.com/pranavraja/apns#NewService
The Connect() function takes filesystem paths to the certificate and private key files. That's too limiting — the server may not have filesystem storage available, or the private key may be considered too sensitive so it might be kept in a Keychain-like store or an LDAP server.
Probably the most flexible way to do this would be for Connect() to take a tls.Certificate as a parameter, and let the caller load the certificate by calling either LoadX509KeyPair or X509KeyPair, the latter of which takes the components as raw byte arrays.
(I just filed the exact same issue as huo-ju/Go-Apns#3. Apologies for copying and pasting the text, but the issue with both packages is identical.)
The text was updated successfully, but these errors were encountered: