6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/4/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#12970] Don't override sticky OPTIONS values with default values.
*
Your Email Address
*
Spam protection
Enter the letters below:
.__ .__ .___.._.. , | \[__) | | \./ |__/[__) | _|_ |
Comment
> >> After analysis, I found that the pkcs7 data is sent in one long line >> and that throws off the OpenSSL parser. >> If I format the data using a max-length of 72 characters, then >> OpenSSL can decrypt the data. > > I am almost 100% positive that the encoded data has a maximum line > length of 76 characters. This is almost certainly a BB bug. > > >> So, my guess is that Horde sends the msg to OpenSSL which can't >> handle it as is. That's one half of the problem. > > Yes, we use the PHP native openssl_pkcs7_decrypt() function. > >> The other half is figuring out if Horde is doing something which >> prevents the BB client from understanding the message it gets or if >> the client only understands messages where the data is on one line. > > Horde_ActiveSync passes all S/MIME messages UNTOUCHED to the client. > >> I couldn't find a spec regarding the maximum amount of characters per >> line allowed in pkcs7 data, so I'm guessing that what they're doing >> is legal and one reason most clients can read it. > > application/pcks7-mime, which is normally base64 transfer-encoded is > limited to 76 characters per line.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers