Thanks for the response Traffic, however that posting was what I was actually referring to in my previous post. That posting seems to have the following problems that are unfortunately not helpful for me:
1) TLS1.0/1.2 is in fact vulnerable to POODLE from what I've read (I understand that posting by you was likely done prior to public knowledge of this), therefore disabling SSLv3 wouldn't help
2) You state to "See also: !hardening for some unrelated TLS security options OpenVPN has", which I imagine refers to
https://community.openvpn.net/openvpn/wiki/Hardening, which is outdated by 20 months and doesn't really answer my question unfortunately.
3) tmack0 alluded that OpenVPN access has taken steps to protect against POODLE, but as you pointed out, this does not apply to the community version
When searching for openvpn's poodle vulnerability, I cant seem to find anything useful since a lot of it. Even OpenVPN's documentation that is 14 months old has not been updated to account for TLS 1.2:
https://community.openvpn.net/openvpn/wiki/Poodle
I understand that all of this is really based off OpenSSL, and that it is possible that no one really knows, and that it is free open source, but unfortunately my company won't give a budget so we are stuck with this.
I hope that my original questions will be answered so I can actually use CFB and GCM ciphers, which from what I'm told will ultimately result in protection against the POODLE vulnerability.
