| Age | Commit message (Collapse) | Author |
|---|
|
same name, do not overwrite a file more than once, but instead add a
counter number to the filename to make a new file that does not exist
in the file system.
|
|
only a small portion of the subtitle (e.g. "Directo" instead of
"Directory Server on some.server.com".)
|
|
when the position for wrapping is at a wide UTF-8 code point.
|
|
In order to produce a crash one needed to use the ^T subcommand and
do a search in a LDAP directory. The crash is produced by changes to
the text in the title bar. Reported by Heinrich Mislik in the
Alpine-info list.
* Add ignore size option to Alpine, which helps users deal with some
servers that compute sizes incorrectly but send complete messages
when users save messages from those servers.
|
|
adding memory freeing calls when necessary.
|
|
user is sometimes asked to import a certificate and sometimes a key.
* Fix a case of memory freed twice introduced in commit 4bf825141c...
|
|
that encrypts password file in case that the new key/certificate pairs
have the same name as the old key/certificate.
|
|
to encrypt a password file in the SMIME setup configuration screen.
|
|
file, writes a non-secure encrypted password file until Alpine is
restarted again.
|
|
Provided by Dennis Davis.
|
|
* Update of copyright notice
* Update to release notes to indicate support of RFC 2971.
|
|
|
|
the certificate to lowercase, which may make Alpine not be able to
read such certificate. Reported by Dennis Davis.
|
|
ldap_unbind_ext to ldap_unbind and add config.wnt.h to git
repository)
|
|
screen to account for the broadened search, but will not replaint the
screen due to scrolling. Suggested by Holger Trapp.
|
|
in signatures, when the option "Validate Using Certificate Store Only"
is enabled. If the user does not wish to save it, validation will fail.
|
|
* Fix typos in documentation (cotainer to container.) Reported by Holger
Trapp.
* Alpine does not remove remporary files created when adding a CA
certificate to a container. Reported by Holger Trapp.
|
|
|
|
user to choose the dictionary used to spell, in case the user
communicates in more than one language. Examples of values for the
variable are "en_US" or "de_DE", etc. Only the first 10 dictionaries
are offered.
|
|
information about the use of a file, but the contents of that structure
changed in Visual Studio 2015, so a new system had to be created to save this
information, that did not depend on the contents of the FILE structure.
|
|
Peter Koellner.
|
|
at the end of a line. Reported by James Mingo.
|
|
bouncing. Suggested after a discussion with Matthias Rieber.
|
|
through the history of directories used to save attachments, while
preserving the given name of the file. Suggested by Peter Koellner.
|
|
|
|
remote server and the private key is not available.
* SMIME: Management of several alternate name (SAN) certificates is
improved. When importing a SAN certificate, also import a certificate
for the filename, besides for the e-mail addresses in the
certificate.
* When saving an attachment, the "^T" command leads to a screen where the
"A" command can be used to add a file. A directory can be added by
pressing "^X" after the "A" command. Added after a suggestion by
Stefan Goessling.
|
|
file containing the certificate, as the name to be displayed in the
certificate management screen for certificate authorities. Suggested
by Matthias Rieber.
|
|
in the certificate management screen. Suggested by Matthias Rieber.
* SMIME: sort certificates by some type of alphabetical order in the
displayed name.
|
|
to a remote container.
|
|
symbolic link by Kyle George from tcpsoft.com to use realpath.
|
|
for certificates stored in a container.
|
|
for certificates""
This reverts commit 1fb52f967889d83c23fdd8f3054f5776351ebe85.
|
|
certificates"
This reverts commit bf714e42e10de6ff6bce677551c791397048caa5.
|
|
in containers.
|
|
being transferred, a local copy was not being retained, and therefore
no copy was being transferred to the remote server.
|
|
|
|
remote containers. Reported by Matthias Rieber.
|
|
* Move manual pages to a "man1" directory.
|
|
would not show those messages if those messages are on top of the
current message in the top of the screen.
|
|
lisblank.
* Clean up some code in pith/smime.c.
|
|
not using it anyway.)
|
|
not all the information on a certificate might be printed on the
screen. The bug was introduced when warnings from clang were cleared.
|
|
in the next search.
|
|
|
|
in system.h.
|
|
though a password file might have not been defined.
* Work on reducing the number of warnings in OSX.
|
|
* Add command line argument -smimedir, which allows to specify
the default path for a directory that contains the public, private,
and ca directories. This is useful in case a user has a backup of
old certificates that cannot be installed in the ~/.alpine-smime
dir.
* Update to alpine man page to include documentation on missing command
line options such as -nowrite_password_cache, -passfile, -pwdcertdir,
and -smimedir.
* Various changes in the code to quell some compiler issued warnings in
Mac OSX. Reported by Joe St Sauver. This includes the removing
deprecated ldap functions from the code and the test in the configure
script. The switch to not deprecated functions is done by the use of
the belvar structure, which is not completely appropriate for what we
are doing, but it is sufficient for our needs. The berval structure
is more appropriate for binary data, but it works well with string
data, which is what we need.
* Various changes in the code to quell some warnings issued by clang
3.5.
|
|
|
|
This subcommand toggles if the saving will be done in binary mode for
text attachments. When a user saves an attachment using binary mode
it will be saved as it was sent, otherwise the attachment will be
transformed to UTF-8 for further transformation through internal and
user defined filters for saving.
|
|
a user wants to save a password before reading the password file.
This makes a difference when decrypting a password file, as the
password file was attempted to be decrypted before the user was asked
if they intended to save such password. Now the logic is that the
user will be asked if they intend to save the password, and if they
agree, then users will be asked to provide the password to unlock
their private key.
|
