Hi developers, Since we are very happy about the fixes on SSL-recording and SizeAssertion from last week that makes Jmeter our choice for testing in many areas, we are motivated to invest more in secure mail testing with JMeter. Therefore, I just wanted to raise the question of https://issues.apache.org/bugzilla/show_bug.cgi?id=38387 again:
1) If we extend the already contributed SMTP-Sampler (bug 45053), will it have equal chance to get into the SVN Head if we use BouncyCastle (BC) http://www.bouncycastle.org/ for crypto operations or not? 2) If not, are there any recommendations (under the assumption that 45053 SMTP-Sampler makes it relatively soon) to make life as easy as possible for a non-BC part to coexist with a BC extension to it? I see some hints on p.13 of http://jakarta.apache.org/jmeter/extending/jmeter_tutorial.pdf, but is there a) an easy way to extend a current Sampler with those extra features without having to remove the smtpSampler.jar from the Jmeter installation once we also want to locally run the extra .class'es that contain BC in our environment b) would it be still interesting for the Jmeter project that we add all the non-BC signing/encryption stuff to the SMTP-Sampler sources (like a GUI for the encryption/signature key files, etc. and interfaces to use them... - perhaps someone else will come up to write classes for under the apache license instead - we currently unfortunately don't have the resources to do this) even though they won't really be usable immediately for non-BC users. Many thanks for any hints in advance! Ralf P.S.: If we are successful on this, we probably ought to add signature verification/decryption to the pop-sampler as well... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
