Age | Commit message (Collapse) | Author |
|
|
|
|
|
Fix read/write of digitalsignature stuff.
don't integrate manual-installs, since it's highly variable.
create correct category for digitalsignature, so it gets written out.
|
|
unknon -> unknown
|
|
Don't log kiss code for now.
|
|
|
|
|
|
|
|
buf/imsg specific code. buf_close() will no force a truncation of the buffer
to the wpos but actually add code in imsg.c to detect and report such silly
behaviour. Makes the buf API a bit more sane.
|
|
we are done expanding aliases/forwards, and cleanup a bit the expansion
code so that I can soon remove some of the duplication.
|
|
is notified so that the session does not hang
|
|
causing them not to be handled when a user's homedir is set to mode 0700. I
still need to do some cleanup and make sure it works as it should, but this
diff provides better behavior than what we had.
|
|
lockspool(1). this means our mbox delivery follows a code path that has
become almost identical to external mda deliveries. this is the first
of a serie of diffs actually...
lockspool(1) suggestion by deraadt@, mail.local(8) idea by jacekm@, and
fix and testing by me
|
|
behavior correctly. Be consistent, use the same naming scheme.
problem noticed by Brad Smith.
|
|
|
|
- Introduce secure_file, based on secure_filename from OpenSSH, it
checks that mbox has right perms, and that path components are
trustworthy, too.
ok gilles@
|
|
since fsync is done in final safe_fclose; ok gilles@
|
|
OK claudio@ stsp@
|
|
|
|
explicit; ok gilles@
|
|
path *; ok gilles@
|
|
ok gilles@
|
|
and queue.inserts.local; ok gilles@
|
|
|
|
vt-switch internally so it's likely to actually survive the suspend.
tested by beck@, sthen@. ok deraadt@
|
|
slow enough
|
|
kernel. a one second sleep has made it go away in all my tests. ok theo
|
|
fails -- which should never happen -- the function does not return and is
accession the NULL set control pointer later on.
Found by Matthew Haub. OK deraadt@
|
|
spotted by Matthew Haub <matthew.haub@alumni.adelaide.edu.au>
|
|
ok gilles@
|
|
|
|
a token so that it is possible to do: smtpctl schedule <message id/uid>
introduce F_MESSAGE_FORCESCHEDULE which lets the runner schedule a message
even if the retry delay has not been expired.
F_MESSAGE_ENQUEUED is a valid flag for a message and should not cause an\
errx() in smtpctl show queue
|
|
and uid do not look wrong. this was not needed earlier because we only deal
with message id's coming from trusted sources, but smtpctl will soon have a
new feature which requires us to deal with user provided message id's.
|
|
frame according to the pfsync header. dont try to parse an unsupported
version of the protocol.
|
|
ok jacekm@ gilles@
|
|
runner_reset_flags would attempt to update envelope, but its
envelope.tmp could be renamed by queue_purge. The fix is to store
envelope.tmp in a place no other process writes to, and
/queue/envelope.tmp is perfect for this.
ok gilles@
|
|
ok gilles@
|
|
ok gilles@
|
|
getnameinfo internally; ok gilles@
|
|
|
|
ok jacekm@
|
|
|
|
ok gilles@
|
|
"For sure!" claudio@
|
|
New Intra-Area-Prefix LSAs are originated when a neighbour
becomes adjacent, or when a neighbour loses adjacency,
or when an interface changes state.
ok claudio@
|
|
We now comply with RFC5340 and move prefixes between the two
ref-types of Intra-Area-Prefix LSAs (router and network).
In case an LSA ends up having all of its prefixes moved to another
one, the LSA is flushed from the LSDB by re-originating with MAX_AGE.
(This does not yet work reliably. We end up having LSAs with zero
prefixes in the LSDB in some cases. Should not affect SPF calculation,
so not much harm done, but will need to be fixed.)
This commit just adds the necessary code to do origination,
but it is not being called yet. This will be done in a separate
commit.
"Looks good." claudio@
|
|
Will soon be done in rde instead.
"Sure but don't wait too long before readding the code in rde" claudio@
|
|
Also syncs other fields the ospfe is syncing to when getting
iface updates from parent process.
None of these fields are used by the rde yet, but state will be
important soon, for proper origination of Intra-Area-Prefix LSAs.
ok claudio@
|
|
about nbr state change.
Intra-Area-Prefix LSAs refer to these LSAs. While not strictly necessary,
it makes sense for these LSAs to be up-to-date in the LSDB before new
Intra-Area-Prefix LSAs are originated.
This change has no effect yet because Intra-Area-Prefix LSAs are
currently originated during updates of LSA types it depends on,
but origination will soon be synced to state changes in the iface
and nbr state machines instead.
ok claudio@
|
|
ospfe was sending state from a local variable which does not
always reflect the true state of the neighbour. The RDE would
end up with an invalid nbr state of zero in some situations.
Send state saved in nbr structure instead, this is always valid.
ok claudio@
|