6b97660a0d
Sort sections.
2011-09-23 16:22:00 +00:00
008d0db94d
Also note /etc/saslc.d.
2011-09-23 15:24:35 +00:00
ce1c27eb07
Build and install MLINKS for the libsaslc(3) functions.
2011-09-23 15:17:31 +00:00
a85aba86f0
Use __dead.
2011-09-16 15:36:18 +00:00
6a878ae49f
Reapply formatting cleanup
2011-09-16 15:36:00 +00:00
6f47b6603c
merge openssh-5.9
2011-09-07 17:49:19 +00:00
7c6477cfd2
new openssh:
...
See http://www.openssh.com/txt/release-5.9
2011-09-06 20:17:08 +00:00
c708dfc2ea
some stuff got removed in 5.9
2011-09-06 20:14:35 +00:00
90ee948ed8
Use __dead
2011-08-29 21:08:54 +00:00
95bd2d4a1e
Remove crypto/dist/heimdal and its associated build infrastructure as
...
it has been replaced by crypto/external/bsd/heimdal.
2011-08-28 16:21:57 +00:00
9f9617f826
Change the location of version.h from the old Heimdal srcs to the
...
new srcs.
2011-08-28 11:20:16 +00:00
1ea30656a2
Change the location of version.h from the old Heimdal srcs to the
...
new srcs.
2011-08-28 10:28:35 +00:00
5cfa560df9
Avoid using non-literal format strings and optimizing code a bit at the
...
same time.
2011-08-25 15:37:00 +00:00
cc096ecebe
msg.c uses non-literal format strings
2011-08-25 15:30:54 +00:00
0a56de1dcb
This file should not have been imported.
2011-08-25 00:25:47 +00:00
84c562e368
Previous here required stdint.h.
2011-08-22 00:24:42 +00:00
cbb586e05f
Allow inherited remote blocks without additional remote statements to
...
be specified in a simpler way. patch by Roman Hoog Antink <rha@open.ch>
2011-08-19 05:36:47 +00:00
5434bb1cbb
Remove gcc-4.5 hacks. I must have fixed them in a different pass.
2011-08-17 05:32:09 +00:00
5573cb4a88
remove gcc-4.5 hacks; gcc-4.5 does not like fileno() to be unchecked, and
...
produces an unhelpful out of bounds array warning, so check it.
2011-08-17 05:30:01 +00:00
0a61f86410
undo junk committed.
2011-08-16 09:43:03 +00:00
6c83058fe2
kill non-literal format strings or document them.
2011-08-16 09:42:21 +00:00
4e1d834d15
add extra cast for systems where sizeof(time_t) < sizeof(intmax_t)
2011-08-16 02:59:00 +00:00
51efa0609e
We shouldn't cast client_time to (intmax_t) because it is a char * not
...
an integer.
2011-08-16 01:14:57 +00:00
b4f44e540e
use intmax_t to print times.
2011-08-15 21:00:49 +00:00
641b42eda3
simplify the code; this is what asprintf() is for, don't re-invent it.
2011-08-14 11:19:51 +00:00
cd00f2949d
Have privilege separation child process exit if the parent exits.
2011-08-12 05:21:50 +00:00
6b77872003
default the format for recovering key data to be "human", rather than hard
...
coding it in the embedded calls.
2011-08-02 07:18:13 +00:00
7c7d9aa184
plug some memory leaks in error paths
2011-08-02 07:16:56 +00:00
5f50489b1b
when matching pubkeys, also return the first (pgp) uid for the key in the
...
resultant key listing
when using json to format keys returned from libnetpgp, also prepare for
machine-readable format ("mr") as well as human ("human"), even though
it's not yet used.
2011-08-02 05:36:45 +00:00
18eab2817e
PR/45200: : J. Hannken-Illjes: Scp hangs after sending:
...
- check for vwrite() instead of read() to avoid read() being renamed by SSP
2011-08-01 15:55:00 +00:00
84e06c949d
revert previous, actually cleanup the *_asn1-template.c files
...
in Makefile.rules.inc. They are generated when -one-code-file
is passed.
2011-07-31 09:58:19 +00:00
7d2b0ea36f
Clean up intermediate asn1 template files
...
(this should reeally be fixed in <${HEIMBASE}/Makefile.rules.inc>
but I don't see where since they are not generated for all asn1 sources)
2011-07-31 06:49:03 +00:00
d38e8168f4
cleanup vars.texi
2011-07-31 06:43:56 +00:00
aa1008d816
Drop @GOTPCREL when accessing local variables. For yet unknown reasons,
...
our version of GNU as decides to silently ignore it. Never versions on
other systems and Clang actually keep it around and create bad object
files. The object files are identical after the changes modulo the GOT
entry in the symbol table.
2011-07-28 20:24:36 +00:00
376bdd7ba0
Workaround around make bug by using an intermediate file/rule.
2011-07-27 03:18:52 +00:00
767a408b3c
Get rid of the "rep ret" trick in places where it is not needed. FWIW,
...
the "rep ret" trick is recommended by AMD as a branch prediction
optimization in certain circumstances (quoting their manual):
- any kind of branch (either conditional or unconditional) that has the
single-byte near-return RET instruction as its target
- a conditional branch that occurs in the code directly before the
single-byte near-return RET instruction.
2011-07-25 19:11:49 +00:00
9c5ebc857f
Works with the integrated assembler again.
2011-07-25 09:36:10 +00:00
f40b364521
Fix obvious logic error
2011-07-25 08:51:10 +00:00
185c8f9719
- Merge conflicts
...
- WARNS=5
2011-07-25 03:03:09 +00:00
9921411534
from ftp.openbsd.org
2011-07-24 15:08:11 +00:00
714fcad23a
Turn AES NI support code into something more readable.
...
i386 and amd64 both tested with their own chroot. No regression observed.
2011-07-22 22:50:55 +00:00
5158e28f3b
Disable Clang's integrated assembler for the AES-NI files for now.
...
Somewhere in this mess of .byte streams, corruption happens. Disassembly
only shows slightly different filling of alignment sequences, further
analysis is needed.
XXX This should be rewritten to be proper assembler code
2011-07-17 19:48:31 +00:00
929391d8b0
remove SSL3_FLAGS_ALLOW_UNSAFE_LEGACY_RENEGOTIATION -- openssl uses
...
another mechanism now, and these remainders break renogotiation with
(at least) tor and postgres
2011-07-07 18:11:18 +00:00
c22e711e00
cpuid and aesni additions for i386
2011-07-05 16:53:58 +00:00
7d2aeb8d2a
more pieces to enable using the assembler routines and aes-ni for amd64
2011-07-05 10:42:54 +00:00
e910cee8f4
fix some define and cleanliness issues relevant when test compiling
...
in dist (which we normally don't do)
2011-07-05 10:29:22 +00:00
0d71cd5d7d
use aes-ni for i386 also: from jym@
2011-07-05 10:25:45 +00:00
3619dd3d7c
version bump second part
2011-07-05 10:06:10 +00:00
fa1a81643b
Fix memset usage.
2011-07-01 02:10:19 +00:00
2008a1289b
get some things off the TODO list
...
when initialising, recognise keys in a different order.
1. read the public keyring
2. if a userid has been specified, use it
3. if not, check the configuration file (~/.gnupg/gpg.conf) for a
default user id
4, only read the secret keyring if we need to (decrypting or signing)
5. if signing, and we still don't have a userid, use the first key in
the secret keyring
6. if encrypting, and we still have no userid, use the first in the
public keyring
ssh keys remain the same as previously.
2011-06-28 03:35:28 +00:00
wiz