I am using the traffic obtained from s_server and s_client sample programs
and the keys that have been negotiated by both the programs to decrypt the
encrypted traffic between the two. That would mean that I am using TCP.
Also, I am running them under the CBC mode.
Vijay K.
On Wed, Jun 25, 2008 a
It's hard to approach this without knowing the mode of operation you
are running CBC, OFB, CTR? Also are you using UDP with varying packet
sizes?
Julian
On Jun 24, 2008, at 10:25 PM, Vijay Kotari wrote:
Hi,
I am using EVP_DecryptUpdate() and EVP_DecryptFinal_ex() to decrypt a
SSL packet th
Hi,
I am using EVP_DecryptUpdate() and EVP_DecryptFinal_ex() to decrypt a
SSL packet that I have captured. The cipher that I am using AES256 and
I can read the application data in cleartext as a result. The problem
comes if the application data size > 8, which I think has something to
do with me u
> I have an desktop/server agent that listen for TCP connections to
> process some information. And now i´m trying to implement privacy
> and authentication to this application, to unsure that only my
> trusted application interact with these TCP agents.
> Another problem is that I'm not sure if
Hello all!
I have an desktop/server agent that listen for TCP connections to process some
information. And now i´m trying to implement privacy and authentication to this
application, to unsure that only my trusted application interact with these TCP
agents.
I started reading the article http:/
On Tue, Jun 24, 2008 at 01:21:09PM -0700, Kyle Hamilton wrote:
> The patent on the RSA algorithm expired several years ago, in 2003.
>
http://en.wikipedia.org/wiki/RSA#History
--
Viktor.
__
OpenSSL Project
The patent on the RSA algorithm expired several years ago, in 2003.
-Kyle H
On Tue, Jun 24, 2008 at 6:44 AM, sathish subramanian
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would like to bundle libssl library with our product. I see that RSA has
> strict patent restrictions, which makes libssl difficu
Technically, the mime-type application/xml requires that ALL content
be encoded in UTF-8. (This is an artifact of XML itself specifying
that it is always UTF-8.)
If it's not valid UTF-8, then it's not valid XML, which (depending on
your environment) may not even need to be evaluated for its signa
Yes, I believe the messageDigest in the ASN.1 dump is, indeed, the hash of
the data that was signed.
javierm wrote:
>
>
Ok following your quoted note, I got the asn1 structure to see what was
inside there:
> Which value contains the hash you mention? Is it the messageDigest?
>
>
Thanks
>
Hi,
I would like to bundle libssl library with our product. I see that RSA has
strict patent restrictions, which makes libssl difficult to bundle. How can
i rebuild libssl to include only DSA and not RSA? If I get around doing
that, can i then build libssl with my product?
thanks
sathish
Oh Boy!! Eureka,
Yes the HEX number in "messageDigest" converted to base64 gives me the MIC
that the trading partner expects, though, I can not figure out how this
value is obtained based on the original content between the first and second
boundary. I calculated the message digest for this "or
Ok following your quoted note, I got the asn1 structure to see what was
inside there:
Which value contains the hash you mention? Is it the messageDigest?
Thanks
jkoehring wrote:
>
>
> Another way to look at it is when the original AS2 message is signed, the
> MIC for the MDN should be ex
12 matches
Mail list logo
