| Age | Commit message (Collapse) | Author |
|---|
|
refresh token and access token in Gmail using the S256 method
and plain method.
|
|
its choices the ps_global->vars[V_XOAUTH2_INFO].current_val.l. Now it will
also use ps_global->vars[V_XOAUTH2_INFO].main_user_val.l. In addition some
of the code in alpine/xoauth2conf.c was moved to the c-client library.
|
|
and the local password cache (password file or system local cache.)
|
|
negotiating a secure connection with a SSL server. Work in
collaboration with professor Martin Trusler.
|
|
to login to outlook, since the original client-id can only be used
for the device method. One needs a special client-id and client-secret
to use the authorize method in Outlook.
|
|
autentication and reveals sensitive login information. Use with care.
Remove your .pine-debug file after using this option.
|
|
as a one time option, in case we need to use a special IMAP ID.
|
|
internally.
* Fixes to some prototyping for code related to authentication.
* Fixes to documentation contributed by Dennis Davis.
|
|
within 60 seconds of expiration of the access token.
|
|
a user to specify the location of server certificates that the user trusts.
|
|
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.
|
|
+ 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.
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
Alexander Perlis for suggesting it and explaining how the method works.
|
|
the windows version of Alpine in a 32-bit environment.
|
|
client-id and client-secret information.
|
|
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.
|
|
select the method to authenticate to an IMAP, SMTP or POP3 server.
Examples are /auth=plain, or /auth=gssapi, etc.
|
|
version 1.3.
|
|
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.
|
|
|
|
|
|
|
|
* If the charset of a message can not be determined, use the value set
in the "Unknown Character Set" option.
* Resizing setup screen will redraw screen.
* Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
in the width ambiguous zone, it will use other means to determine
the width, such as call wcwidth.
|
|
* Introduce the option "Validate Using Certificate Store Only", and
make it the default. This will make Alpine check for the validity of
signatures in certificates that a user has installed in their
system, and not in the certificates that come with the message. A
user can override this, although is not recommended, by disabling
this feature.
* When viewing a signed message, the ^E command would present an
empty screen or Alpine would crash because when Alpine would get the
PKCS7 body of the message from body->sparep, it would not decode it
properly due to the new way in which the sparep pointer is encoded
that was introduced in version 2.19.991.
* When a signed message is forwarded, the message might not be filtered
correctly, and mime information might make it into the body of the
forwarded message. In order to produce this, the message must be
forwarded from the index screen and not be opened. The reason why
this makes a difference is because opening a signed message changes
its body structure. The reason why a person could forward a message
before reading it is because the person could already be aware of
the content of the message (e.g. the message is in the sent-mail
folder).
* When a message fails to validate and the body is saved from the server
for validation, be careful in the way that body part pointers are
set, in order to do this we split the mail_body function into two
parts, one that gets the body, the other that gets the section of
the body. The new function that gets the section of the body
(mail_body_section), is used to assign pointers of the reconstructed
new body.
* When a container has not been defined, transferring messages to a
container will succeed, and the name of the container will be
written on screen.
* When Alpine is receiving the envelopes from an imap server, it
attempts to generate the index line immediately; while doing so it
might need to compute a score, and for this, it might need to go
back and do some operation in the same imap server. In this case,
Alpine will crash with a "lock when already locked" message. In
order to avoid this crash, a new check in match_pattern was added to
Alpine to avoid the second trip to a server that is busy sending us
envelopes. Reported by Peter Koellner.
* Update copyright notice in mswin.rc and pmapi.rc, as well as first
time user notice and special request notice.
* Alpine cannot handle correctly some characters in the Windows-1256
character set, which might lead to a crash or a corruption in the
screen. Work was done to contain the bug. A more complete fix will be
done in a future release. Reported by Professor Robert Funnell.
* Decode the name of attachment names, so they can be written as part
of the description of the part.
* When transferring certificates to a local container, create container
with default names PublicContainer, PrivateContainer and CAContainer,
as appropriate for these files, unless the user has provided some
other names.
|
|
* Upgrade UW-IMAP to Panda IMAP from https://github.com/jonabbey/panda-imap.
* Replace tabs by spaces in From and Subject fields to control for size in
screen of these fields. Change only in index screen display.
|
|
* Fix in configure script for recognition of SSL files in Ubuntu 12.04
* Alpine does not attempt to automatically reopen a collection that
was not opened due to cancellation by the user. Instead, the user
must try to open it explicitly.
* few improvements on new /tls1, /tls1_1, etc. options.
|
|
* Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
server to use different ways to connect using ssl, for example
{server.com/tls1} will attempt to connect to server.com at the ssl
imap port (port 993) and establish a connection using TLSv1. These
flags can be used in conjunction with the /ssl flag, the ssl flag is
redundant. Conversely, however, the /ssl flag does not imply any of
these flags; the /ssl flag means SSLv3 or, if not available, SSLv2 in
the SSL port.
* WebAlpine: add _GNU_SOURCE to make pubcookie build.
* On my way to make 'make dist' and 'make distcheck' actually work.
|
|
|
|
a url by
a browser.
|
|
|
