| Age | Commit message (Collapse) | Author |
|---|
|
to login. Reported by Frank Tobin.
|
|
username, and tenant.
* If a user has more than one client-id for a service, Alpine tries to
asks the user which client-id to use and associates that client-id to
the credentials in the XOAUTH2 configuration screen.
|
|
|
|
Reported by Marco Beishuizen.
|
|
using /tls
on an insecure connection. However, if the connection is PREAUTH, Alpine
will not upgrade the connection to a secure connection, because a client
must not issue a STARTTLS to a server that supports it in authenticated
state. This makes Alpine continue to use an insecure connection with the
server, exposing user data. Reported by Damian Poddebniak and Fabian
Ising, from Münster University of Applied Sciences.
|
|
documentation,
fixes in the configuration screen, and documentation on what is needed in each
structure defining each service.
|
|
Based on documentation suggested by Andrew C Aitchison.
|
|
|
|
|
|
|
|
|
|
http replies can come, so
that http_* functions return the body and not the headers of a reply.
|
|
return the headers
of a http reply. So, http_get returns the text retrieved retrieverd, without headers. This allows for
simplification of the mm_login_oauth2_c_client function.
|
|
/starttls instead of /tls. This should cause less confusion in Alpine users
in the future.
|
|
|
|
|
|
even though we do not report the full command used.
|
|
a text explaining the basic steps on how to configure fully Alpine with Gmail
was added. In addition, some issues introduced while included OAUTHBEARER
were also fixed.
|
|
authentication.
|
|
extra debug information as messages in the screen.
|
|
support for the NTLM authenticator is compiled into Alpine.
|
|
protocols (SMTP, NNTP, POP3) as some SMTP servers do not support a
round-trip two step authentication. For example, davmail does not
support PLAIN authentication in SMTP using the challenge-response
scheme. Implemented after a report by Geoffrey Bodwin.
|
|
of CA certificates. This complements the variable system-certs-path that
gives the location the directory that containes CA certificates.
|
|
of Alpine. Reported by Bob Bernstein.
|
|
Alexander Perlis for suggesting it and explaining how the method works.
|
|
|
|
memory in file http.c, and move Pico version to 5.10.
|
|
the windows version of Alpine in a 32-bit environment.
|
|
fixed those that belong to the source code of Alpine and do not come
from an external source. List contributed by Jens Schleusener.
|
|
client-id and client-secret information.
|
|
file prevented users from actually saving their passwords in Windows
and MAC OS. Fix the code so that passwords will be saved. Also,
update the documentation of this feature.
* Fix a buffer overflow bug in the XOAUTH2 code (off by one error).
* Update PC-Alpine to work with Libressl version 3.0.2 instead of
version 2.5.5 (update build.bat and lib files from the LibreSSL
build).
* Erase SSLXXXXXX file.
* ssl_nt.c actually directs the code to ssl_libressl.c or ssl_win.c.
The file ssl_libressl.c is the file ssl_unix.c from the unix osdep
directory. The file ssl_win.c is the native SSL windows code. The
Unix side provides S/MIME support for Alpine and the latest
encryption protocols support for Alpine when connecting to a secure
server, while the windows side provide TLSv1_3 support for Alpine,
but not S/MIME support.
In order to provide unix code for TLSv1_3 (once LibreSSL supports it)
edit the file os_nt.c and remove the comments on the #ifdef section.
This would provide both TLSv1_3 and S/MIME support with unix code. On
the other hand, when we provide TLSv1_3 with the Windows code we need
to undefine DF_ENCRYPTION_RANGE, and this is done in the file
include/config.wnt.h. The way this is done as of this moment is by
commenting an #else directive that preceedes this #undefine.
* Update makefile.nt and friends in the windows side to account for the
addition of XOAUTH2, and the use of only ssl_nt.c when dealing with
Alpine.
* Define SMIME_SSLCERTS as c:\libressl\ssl\certs, so that these
certificates be considered while checking a digital S/MIME signature.
* Improvements to the SMARTTIME24 token to account for changes in year.
|
|
during authentication using CRAM-MD5. The intention was to ignore the
challenge in the PLAIN authentication. This made Alpine fail to
authenticate when using the CRAM-MD5 authenticator. Reported by Stefan
Mueller.
|
|
non-empty challenge in a smtp server.
|
|
|
|
to user's request.
|
|
connection is closed while the post is being composed, but later the
post is attempted to be sent. In some instances, the stream may be
open and closed during this time, but Alpine does not realize the
connection was closed and attempts the post without a netstream,
producing a crash.
|
|
|
|
was being allocated. Based on a report by Erich Eckner.
|
|
Gmail.
|
|
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.
|
|
when added support for internationalization in folders. Based on a
report by Michael Rutter.
|
|
select the method to authenticate to an IMAP, SMTP or POP3 server.
Examples are /auth=plain, or /auth=gssapi, etc.
|
|
server. Based on a report by Stefan in the Alpine-info mailing
list.
|
|
email via SMTP, but still report the previous error to the client.
|
|
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.
|
|
version 1.3.
|
|
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.
|
|
character in UTF-8, but 0xfff8 is undefined.
|
|
|
|
servers that implement the X-GM-EXT-1 capability (such as the one
offered by Gmail.) This allows users to do selection in Alpine as if
they were doing a search in the web interface for Gmail.
|
