| Age | Commit message (Collapse) | Author |
|---|
|
|
|
keystroke sequence of commands is active. Based on a report from Holger
Trapp.
|
|
|
|
problems exist, so I can go back to the exact bits that caused the
problem.
|
|
of Openssl that do different things. I need to understand them
better. In the mean time, we go back to the original code.
|
|
consistent in what it signs. Problem reported by Björn Krellner.
|
|
options.
|
|
version 3.0.
|
|
user agrees to save a certificate of another user, use the saved
certificate immediately to verify the smime message. Reported by
Stefan Mueller.
|
|
submitted in 2009, but resubmitted by Erich Eckner on 2019.
|
|
fails to add a trailing line to signed text. Reported by Stefan Mueller.
|
|
and not the new calls.
|
|
was being allocated. Based on a report by Erich Eckner.
|
|
|
|
Reported by Matt Roberds to the Debian bug system at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886370.
|
|
Gmail.
|
|
"mechanic" in comp.mail.pine.
* Configure script modifications to set the ldap-dir value correctly.
* Fix some typos in documentation.
|
|
that fix the following startup crashes:
* Crash when Alpine started with empty url fragment;
* Crash when Alpine started with option last-time-prune-questioned
in wrong format;
* Crash when Alpine started with printf formatting characters from
command line; and
* Crash when Alpine started with an extremely long command line
option.
* Crash when Alpine is started with the wrong piped input when
opening a folder from the command line. Reported by Mateusz
Kocielski from LogicalTrust.
|
|
Eckner.
|
|
a. Add a new variable: encryption-protocol-range, which can be
used to specify the minimum and maximum versions of the TLS
protocol that Alpine will attempt to use to encrypt its
communication with the server.
b. Add support for the Server Name Identification (SNI) extension
needed for TLSv1.3.
c. Remove the DTLS code. It was not being used.
|
|
of the file, if this is in the Content-Disposition parameter.
Based on a report by Holger Trapp.
|
|
emails, the filenames will be displayed in RFC1522 representation,
instead of in decoded form. Reported and patched by Wang Kang.
|
|
for big amounts of time while displaying messages in the screen.
Reset sleep time to 5 seconds in case it finds it needs to sleep
more than 5 seconds or a negative amount of time.
|
|
because of that, Alpine sets their encoding to quoted-printable, in
contradiction to RFC 2045. We handle this by keeping the encoding
reported by the server. Based on a report by Holger Trapp.
|
|
released by the system.
|
|
and short-lived until release of Pine 4.43 (released November 28,
2001.) Also update message to mean what Alpine is trying to do
(forwarding, not answering.)
|
|
Content-Transfer-Encoding: QUOTED-PRINTABLE, Alpine will stop
processing that message. Later this causes Alpine to crash because
when it displays messages, it assumes that both header and body parts
are processed. Reported by Mark Crispin in 2010, in the Alpine-info
list (message with subject "crash bug in
alpine/mailpart.c:format_msg_att()") with no example, and reported
now by Holger Trapp, with an example.
|
|
removing parameters of the content-type header.
|
|
then forwarding the message will set the first part to be flowed, and
sent that way even when the option Do Not Send Flowed Text is
enabled.
To avoid this issue, we remove any flowed text parameters from the
body of the message, so we create a "remove_parameter" function, and
then we set the flowed parameter only when the user requested.
Reported by Holger Trapp.
|
|
they are windows-1252, so we treat them as windows-1252 from the
beginning. If we did not make this change, we might see '?'
characters in the displayed message, without an apparent explanation
of this fact. Reported by Holger Trapp.
|
|
a failure using an SMTP server. This was due to c-client sending a
RSET command after the failure and Alpine reporting the reply of this
command.
|
|
S/MIME,
and then reenabled it. This crash was due to a double free of memory. To avoid
this in the future, we created a function free_x509_store(), which whenever
called, will only free memory once. A similar crash would occur when one
attempted to enter the S/MIME configuration screen if S/MIME was turned off.
In this case, Alpine would try to dereference a null pointer.
|
|
version 1.3.
|
|
decoded with escapes removed. Similarly do the same for other
headers.
|
|
Alpine from a subshell. Reported by Andreas Schamanek.
|
|
signing first and encrypting second, which makes Alpine fail to parse
the signed data after encryption. Reported by Holger Trapp.
|
|
LibreSSL in connecting to external servers. This complements the
changes to support S/MIME. In particular, we add support for
validation of certificates by using C:\\libressl\ssl\certs as the
place to save CA certificates. In order to help users, some
certificates are distributed. TODO: Kerberos port, w2k.
|
|
we need to allocate memory for storing the resolved path. Reported by
Fabian Schmidt.
|
|
avoid memory leaks when trying to get the opening text a second time,
and get the actual opening text for html messages that are part of a
multipart/* text. In addition, Alpine caches this text, so that operations
such as resizing, or marking a message deleted, does not make Alpine
recompute this text.
|
|
library until the development header have been found, and update
C_CLIENT_AUTHS to not to have a trailing space.
|
|
character in UTF-8, but 0xfff8 is undefined.
|
|
coming from the configure script and imap/Makefile. Remove the double
definition from imap/Makefile. Reported and patched by Wang Kang.
|
|
|
|
is used. The revert to using code for the Windows operating system.
Reported by Andrew Ho.
|
|
multipart/mixed message that contain a signed part.
|
|
the full text of the original message in a multipart type attachment,
instead of the first body part of the replied message.
|
|
multipart/signed, Alpine will include the text of the original
message in a reply message, instead of including a multipart
attachment. Suggested by Barry Landy.
|
|
part. In this case, these attachments are not included in a reply,
even if the option "Include Attachments in Reply" is enabled. We
include these attachments in a reply too in this case (experimental.)
|
|
|
|
|
