Imported from previous forum
What kind of encryption is generally supported by FIX Engine or popular in commericial implementation?
As per specs:
The use of SecureData(91) to encrypt FIX message has been deprecated in FIXT.1.1 The use of custom encryption is no longer recommended. Refer to the Information Security White Paper from the FIX Information Security Subcommittee.
What kind of encryption is generally supported by FIX Engine or popular in commericial implementation?
As per specs:
The use of SecureData(91) to encrypt FIX message has been deprecated in FIXT.1.1 The use of custom encryption is no longer recommended. Refer to the Information Security White Paper from the FIX Information Security Subcommittee.
Check the white paper here:
http://www.fixprotocol.org/documents/5098/FIX%20Security%20White%20Paper-1.8-FINAL.pdf
In short, if you’re doing encryption via the FIX engine software or an application level proxy, then SSLv3 or TLS. I have heard of support for these in commercial products.
FIX can also be secured at the network/VPN level. In that case, an engine doesn’t really support encryption, the underlying network does this automatically.
Just a note: Open source engines as QuickFIX/J also support encryption using SSL.
Cheers, Jörg
What kind of encryption is generally supported by FIX Engine or popular in commericial implementation?
As per specs:
The use of SecureData(91) to encrypt FIX message has been deprecated in FIXT.1.1 The use of custom encryption is no longer recommended. Refer to the Information Security White Paper from the FIX Information Security Subcommittee.Check the white paper here:
http://www.fixprotocol.org/documents/5098/FIX%20Security%20White%20Paper-1.8-FINAL.pdf
In short, if you’re doing encryption via the FIX engine software or an application level proxy, then SSLv3 or TLS. I have heard of support for these in commercial products.
FIX can also be secured at the network/VPN level. In that case, an engine doesn’t really support encryption, the underlying network does this automatically.
Just a note: Open source engines as QuickFIX/J also support encryption using SSL.
And it’s also possible to enable any engine for SSL/TLS by using an external open source application-level proxy called stunnel.