| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5306
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5305
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5304
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5303
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5302
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5301
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5300
|
|
|
|
|
|
| |
In fact, these are linux kernel bugs, hopefully fixed in Linux 2.6.30.
svn path=/branches/BRANCH_6-3/; revision=5299
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5298
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5297
|
|
|
|
|
|
| |
...and postpone for fetchmail 6.4.
svn path=/branches/BRANCH_6-3/; revision=5296
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5295
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5294
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5293
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5292
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Progress tickers had been used inconsistently for a long time, and
documentation was outdated, too. Factor out common code to ease
maintenance, use the report_flush() function, and add and use a macro
(want_progress()) to determine if progress ticker output is desired.
This makes for a much more consistent look on screen and in logfiles and
should be much easier to fix later on.
TODO: test syslog output.
svn path=/branches/BRANCH_6-3/; revision=5290
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5289
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5288
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5287
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5286
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5285
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5284
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5283
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5282
|
|
|
|
|
|
|
| |
Recursive Makefiles are expensive and inconcise, so move the
m4/Makefile.am contents here and remove m4 from SUBDIRS.
svn path=/branches/BRANCH_6-3/; revision=5281
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5280
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5279
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5278
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5277
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5276
|
|
|
|
|
|
| |
distinguished" as a TODO item.
svn path=/branches/BRANCH_6-3/; revision=5275
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5274
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5273
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5272
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5271
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make the introduction a bit more catchy so as to guide people to G3
right away.
In G3:
- some information was given twice. Remove the duplication.
- Add env LC_ALL=C so that people send in information in English and
POSIX locale, we cannot handle i18n-ed reports.
- Remove IMAP advocacy. Doesn't belong here, and ESR's IMAP-over-POP3
advocacy is neither technically substantiated nor warranted today.
svn path=/branches/BRANCH_6-3/; revision=5270
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5269
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5268
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5267
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5266
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5265
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5264
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5263
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Daniel Richard G. writes:
| I was clearing out an old Fetchmail SVN checkout I had lying around
| here, and came across one small change that I forgot to send in.
|
| In socket.c, there's a bit of code that compares SSL certificate
| fingerprints: [...]
|
| That strcmp() call should be an strcasecmp(). At one point, I
| encountered a certificate where the fingerprint's hex digits were in a
| different case than what was expected, and the connection attempt failed
| because of that. Not exactly what you'd call a potential MitM attack
| :-)
He's right, we can compare case-insensitively without sacrificing
fetchmail's security, so let's just do that for the sake of ease of use.
svn path=/branches/BRANCH_6-3/; revision=5262
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5261
|
|
|
|
|
|
| |
interface.c. Courtesy of Nico Golde, Debian.
svn path=/branches/BRANCH_6-3/; revision=5260
|
|
|
|
| |
svn path=/branches/BRANCH_6-3/; revision=5259
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"The AC_CANONICAL_TARGET macro and the $target_os variables are used for the
target of compilers and other code-generation tools, and should not be used
during cross-compile of generic software. Replace them with
AC_CANONICAL_HOST and $host_os instead, as they should have been from the
start.
For a breakdown of what host, build and target machines are, please see
http://blog.flameeyes.eu/s/canonical-target ."
svn path=/branches/BRANCH_6-3/; revision=5258
|
|
|
|
|
|
| |
Fix grammar (validate stricter -> validate more strictly).
svn path=/branches/BRANCH_6-3/; revision=5257
|