Hi Yehuda, I've encountered this problem some time ago too. The simple fix was to limit the country field to two characters only. I'm not sure why you're exception never makes its way to the page (there's a try/catch block, right?)-- perhaps it's because errors are disabled in php.ini...
Anyway, the pfSense copy that I've worked on has suffered significant bitrot-- it's a bit hard to export the WebGUI validation fixes that I've made and contribute them back to the community. I hope I can sync them to the latest pfSense... :( [ simon.cpu ] On Fri, May 27, 2011 at 4:46 AM, Yehuda Katz <yeh...@ymkatz.net> wrote: > I am working on http://redmine.pfsense.org/issues/1437 and running into a > strange problem and I thought I would ask about it before I spend a long > time digging through the source. > I thought the only foolproof way to return openssl errors would be to wrap > them in an exception and throw it, but it seems that the exception never > makes its way to be visible on the page. Even stranger, the action that does > happen appears to be random. I try to generate a CSR with an invalid country > field. sometimes the CSR is generated, other times a self-signed-cert is > generated (I did not test them and they are probably not valid, but > something is added to the config), but the exception never shows up. > Comments? --------------------------------------------------------------------- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
