| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
attributes even if already outside alternate screen mode. GitHub issue
1789.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
While here, also insert missing whitespace before punctuation.
|
|
|
|
|
|
| |
skip PCI host bridges and devices that aren't there.
ok patrick@
|
|
|
|
|
|
|
|
|
|
| |
which is now supposed to be opaque.
OK tb@
I checked that all the information contained in comments in the
display is available from the appropriate places in RSA_meth_new(3)
and RSA_set_flags(3). Note that the comments regarding "mod_exp",
"init", and "finish" were half-misleading simplifications, anyway.
|
| |
|
|
|
|
|
|
| |
there's some more work to do in this space, but this helps us start.
ok kettenis@
|
|
|
|
|
| |
Update the documentation.
OK tb@ jmc@
|
|
|
|
| |
OK tb@ jmc@
|
|
|
|
|
| |
One could always use them on the command line and acme-client would do
the right thing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the following improvements:
- Shift the middle bar of the upper case 'G' one pixel down in the 12x24
version
- Shift lower case 'k' character right, for better alignment in the 12x24,
16x32, and 32x64 versions
- Make upper case 'X' thicker in the 16x32 and 32x64 versions
- Make upper case 'V' thicker in the 32x64 version
- Make lower case 'g' character smoother in the 16x32 and 32x64 versions
- Add some artefacts on each side of the lower case 'i' characters
OK kettenis@, naddy@, deraadt@
|
|
|
|
|
|
|
| |
larger than 256KB not 128KB to cope with the 06-8e-09 microcode which is
currently 193KB.
Reported and tested by Paul de Weerd. Matches a diff from claudio@
|
|
|
|
|
|
|
| |
* Add a missing comma
* "cdrom" should be "CD-ROMs"
ok espie@ jmc@
|
|
|
|
|
|
| |
on 32bit platforms which cause incorrect results when adding a block
>=512M in size. sha1 patch from ante84 at gmail.com via openssh github,
sha2 with djm@, ok tedu@
|
|
|
|
| |
usb.4: sort ukspan entry and sync with Nd
|
|
|
|
|
|
| |
These references were misleading because these functions are no
longer used internally and applications should not call them either.
Issue brought up by tb@.
|
|
|
|
|
|
| |
to start, otherwise commands like lsk which start the server again can
end up looping infinitely. Also make the first client exit
correctly. Problem reported by Wael M Nasreddine.
|
| |
|
| |
|
|
|
|
|
|
|
| |
PKCS5_PBKDF2_HMAC(3) to the top level page evp(3). The leaf pages
still have backlinks to the group entry page EVP_DigestInit(3),
which is enough.
Redundancy and asymmetry pointed out by tb@.
|
| |
|
| |
|
| |
|
|
|
|
| |
written by Cody Cutler <ccutler at csail.mit.edu>
|
| |
|
| |
|
|
|
|
| |
ok patrick@
|
|
|
|
|
|
| |
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..
|
|
|
|
| |
there is no downside for others.
|
|
|
|
| |
knweiss at gmail.com via -portable.
|
|
|
|
|
|
| |
addresses about every 10 - 30 seconds. Reduce log level to debug to
stop the syslog spam.
OK reyk
|
|
|
|
| |
ok guenther@ yasuoka@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clean up the possible nexthop overrides to better match the RFC.
- set nexthop self is still overriding all other decisions
- set nexthop no-modify has only relevance for ebgp multihop links
Instead of using the router locall address the nexthop is passed unmodified
- set nexthop <address> depends on BGP session type
* for IBGP sessions the address will be used unless it is the same as the
remote peers address
* for directly connected EBGP sessions the address is only used if the IP
is part of the connected network (no matter what other flags are used).
* for multihop EBGP sessions it depends if no-modify was also set
Adjust manual page to explain this properly.
"probably OK" job@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(ACME)" to be able to talk to the v02 Let's Encrypt API.
With this acme-client(1) will no longer be able to talk to the v01
API. Users must change the api url in /etc/acme-client.conf to
https://acme-v02.api.letsencrypt.org/directory
Existing accounts (and certs of course) stay valid and after the url
change acme-client will be able to renew certs.
Tested by Renaud Allard and benno
Input & OK benno
|
|
|
|
|
|
|
|
|
|
|
| |
The additions help while developing mg by not having to go into gdb to
see somethings mg believes about itself. The extra data shown could be
removed in future, but it is benign so perhaps it could stay.
Also, do not fake a '\n' on the end of buffer. It is confusing.
However do not change the lie about '\n' being on the end of every
line within the buffer. Hopefully, one day, that will no longer be a
lie.
|
|
|
|
|
|
| |
this puts the timestamp, rx drops, and hash fields in the right place.
ok jmatthew@
|
|
|
|
|
|
|
|
|
|
| |
this is instead of passing a pointer to the counter.
while here use byte swapping loads and stores, which is mostly a
nop cos i dont think we have an LE arch with swapping memory
operations.
ok jmatthew@
|
| |
|
|
|
|
|
|
| |
ok remi@ (who did the same change to ospfctl, ospf6d, and ospf6ctl)
ok denis@
some grumbling from sthen@ and bluhm@ who didn't want output changed.
|
|
|
|
| |
tested by and ok patrick@
|
|
|
|
| |
to work without a path in addition to with one. bz#2999, ok djm@
|
|
|
|
|
|
|
|
| |
- Adapt openssl(1) gendsa command to new option handling.
- Add lacking ciphers and passout description in openssl.1 manpage.
- Describe paramfile as argument in openssl.1 manpage.
ok bcook@
|
|
|
|
|
|
|
|
|
| |
systems. There is no guarantee that the TSCs on different cores are
synchronized when the OpenBSD kernel boots and we don't have code to
synchronize them ourselves. This affects both AMD and Intel CPUs and
even cores on the same socket can by out of sync.
ok deraadt@, sthen@
|
| |
|
| |
|
| |
|