Age | Commit message (Collapse) | Author |
|
|
|
OK canacar@
|
|
|
|
existing (but undocumented) flag from the usage of ospf6d;
documentation tweaks; while here, synchronize synopsis and usage.
ok claudio@
|
|
Let aldap_freemsg allow for a NULL ber_element tree, since it's now
possible to pass one in.
"looks fine to me :-)" aschrijver@
|
|
|
|
the duplicate database headers seen all the time.
|
|
changes by myself.
|
|
killed. From Stefan Sperling
|
|
the callers should take care of getting the byte order right. While there
remove the opts[123] from the hello_hdr and use LSA_24_* to handle this
nasty fields instead. Now router LSA have the correct flags set.
|
|
work for IF_TYPE_BROADCAST networks.
Initial diff by Stefan Sperling, some additional work by myself
|
|
From Stefan Sperling
|
|
From Stefan Sperling's diff collection
|
|
some macros to handle the 24bit insaneness.
rfc5340 syncup by Stefan Sperling, the insanity is mine
|
|
struct nbr to identify the neighbors correclty.
From Stefan Sperling stsp (at) stsp.name
|
|
possible database desciption files to the RDE. NBR_EVT_NEG_DONE sends an
imsg to the RDE to bring the RDE in the correct state for the database
exchange when doing this the wrong way the RDE will issue errors.
From ospfd (rev. 1.23 of database.c) via Stefan Sperling
|
|
over mulitple hops and causes bgpd to close the connection. This is what
the RFC requires us to do but the result is a DoS against all OpenBGPD
routers when somebody injects such a bad optional transitive attribute
because the intermediate routers don't give a damn about it.
As a result we now ignore such bad prefixes and don't allow them in the
decision process. The handling of optional transitive attributes needs to
be rethinked because all of them can be abused in such a way.
Idea OK by a few + henning@, tested myself against my crappy regress test
suite that needs way more work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
to use this interface consistently; ok chl@ gilles@
|
|
|
|
Hardcode it instead: 5 is a popular choice across the tree; ok gilles@
|
|
|
|
discussed with dlg@
|
|
|
|
if msg is delivered between readdir and opendir, or readdir and
fopen, etc. etc.
Be more unforgiving about errors other than ENOENT, and err()
if they happen, not just warn().
ok gilles@
|
|
|
|
|
|
don't need it to return NI_NUMERICHOST conversion because there's
no reason not to do it in smtp; ok gilles@
|
|
|
|
From: Nicholas Marriott <nicholas.marriott@gmail.com>
|
|
is zeroed in MAIL FROM handler; ok gilles@
|
|
|
|
- unlike starttls, ssmtp sets the F_SECURE flag on session before helo/ehlo
handlers are called. this means that if we clear all flags in helo/
helo handlers, we prevent smtpd from advertising AUTH as it will do
so only for F_SECURE sessions. This commits unbreaks SMTP AUTH with
smtp sessions. Problem spotted by James Turner <james@bsdgroup.org>
|
|
From: Nicholas Marriott <nicholas.marriott@gmail.com>
|
|
From: Nicholas Marriott <nicholas.marriott@gmail.com>
|
|
following line, this commit brings support for the latter which was
not supported yet.
- AUTH LOGIN is now supported, allowing smtp auth support on clients that
do not support AUTH PLAIN (ie: my mobile phone for instance ;)
|
|
- remove non-functional -v option from docs/usage()
feedback/ok millert otto
|
|
- update smtpd.conf.5 just to provide an example, a better description of
"enable auth" will come when im done implementing it ;)
|
|
supported, AUTH LOGIN will follow soon. AUTH will only work if a
listen directive has "enable auth" keywords, AND session is safe
(ssmtp or starttls).
|
|
Mick Hohmann <mick at IM dot net>
|
|
|
|
|
|
is not supposed to happen but better safe than sorry.
suggested by jacekm@
- while at it, remove the locking of delivery file we create when doing a
Maildir delivery. the purpose of Maildir is to prevent the need
for locking in the first place ... I must have been tired that day.
|
|
is not good at all. As a result, under heavy load messages would be
kept in queue, and delayed for hours just because we failed locking
a few times. This commit makes smtpd distinguish between lock fails
and "regular" temporary fails.
- delivery scheduler will reschedule immediately a message that couldn't be
delivered because of a lock fail. If we fail to lock too many times
we fallback to previous "delay increase" logic.
"looks sane" jacekm@
|
|
quickly as possible; it fails under temporary error conditions,
letting caller react appropriately.
ok gilles@
|