| Age | Commit message (Collapse) | Author |
|---|
|
internally.
* Fixes to some prototyping for code related to authentication.
* Fixes to documentation contributed by Dennis Davis.
|
|
Some SMTP servers send a non-empty initial challenge, causing
Alpine to cancel the authentication (in accordance to RFC).
Patch was submitted by Ignacio Reguero, but written by Jarek Polok,
to the re-alpine project (see https://sourceforge.net/p/re-alpine/bugs/16/)
Patch was resubmitted here, but the code was modified in an
equivalent but different way.
|
|
|
|
it might crash due to an incorrect freeing of memory. Reported by Wang Kang.
|
|
within 60 seconds of expiration of the access token.
|
|
because
the call to vfork inside a vfork causes an error EINVAL; however, the same
calls are not causing trouble in other systems, so they are going to stay there.
Reported and asisted by Wang Kang.
|
|
a user to specify the location of server certificates that the user trusts.
|
|
in Windows 10, and it should work in Windows 8.1. It needs testing in
Windows 7 and Windows Vista.
|
|
authorization to read email. One is called "Authorize" and the other "Device".
Some servers support both, some only one. For servers that support both, Alpine
will ask if it does not know which method to choose. Inspired by a conversation
with Pieter Jacques.
|
|
Now w32 and wnt are the same code, so we are only left with wnt
and wxp.
|
|
|
|
+ Alpine does not generate Sender or X-X-Sender by default
by making [X] Do Not Generate Sender Header the default.
+ Alpine does not disclose User Agent by default by making
[X] Suppress User Agent When Sending the default.
+ Alpine uses the domain in the From: header of a message
to generate a message-id and suppresses all information
about Alpine, version, revision, and time of generation
of the message-id from this header. This information is
replaced by a random string.
|
|
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.
|
|
OAUTHBEARER and XOAUTH2. This avoids using these authentication
methods when other authentication methods are still working.
|
|
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.
|
|
ARRC, as these are inherited from values set in the configure script,
which in turn can be inherited from environment variables. This
implies that to build c-client one needs to specify these variables,
and since this is not being built as a stand-alone library anymore, we
take these values from the configure script. Submitted by Robert
Siebeck.
|
|
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 this writing, the port w32 is the same as the port wxp, but it
is intended to target other 32 bit operating systems.
|
|
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.
|
|
location of the directory where folders are located. In PC-Alpine
this must be C:\libressl\ssl\certs. The C: drive can be replaced by
the name of the drive where the binary and DLL files are located.
|
|
|
|
machines that cannot be updated. Long story short: Always use the
command "build wnt" to build Alpine. If that does not work, try
"build w32", which is for machines that are too old and do not have
any way to use modern encryption protocols such as TLSv1.2.
The version of Alpine built in modern machines will be called
alpine.exe, and the binary built with the port w32 will be called
alpine32 in the repository. All other binaries can be downloaded from
the main web site, and they will not have the suffix "32" there.
|
|
|
|
memory in file http.c, and move Pico version to 5.10.
|
|
the windows version of Alpine in a 32-bit environment.
|
|
List contributed by Jens Schleusener.
|
|
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.
|
|
PC-Alpine.
|
