| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
- add __unreachable() after functions that can return but won't in
this case, and thus can't be marked __dead easily
|
| |
|
| |
|
| |
|
|
|
| |
https://www.reddit.com/r/mythbusters/comments/3wgqgv/the_origin_of_the_remember_kids_the_only/
|
|
|
| |
https://www.ieee-security.org/Cipher/ConfReports/conf-rep-Crypto95.html
|
| |
|
| |
|
| |
|
|
|
| |
From John Hein, via Nikolai Lifanov. PR misc/52684
|
|
|
| |
should fix infinite loops reported in some cases.
|
|
|
|
|
|
| |
Mark the documentation in dc(1), gprof(1), rogue(6) and fsck_ffs(8) with
the .roff flag in SUBDIR.
Sponsored by <The NetBSD Foundation>
|
| |
|
| |
|
|
|
|
|
|
| |
programs there; make all Makefiles that use bsd.hostprog.mk include it.
Namely turn off MKREPRO and don't make lint, man pages, info files etc.
Remove the Makefile.inc files that contained these same settings, and
remove the settings from Makefile.host
|
|
|
| |
ok pgoyette@ silence dholland@
|
|
|
| |
ok pgoyette@ silence dholland@
|
|
|
|
|
|
|
| |
While here, don't re-renter pro mode
PR bin/52973
ok maya@ dh@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
battlestar was missing some {} in its insane printf()+puts() usage.
this is a literal code sequence i found:
printf("The blast catches ");
printf("the goddess in the ");
printf("stomach, knocking ");
puts("her to the ground.");
printf("She writhes in the ");
printf("dirt as the agony of ");
puts("death taunts her.");
puts("She has stopped moving.");
no lines inserted or removed.
tetris' checkscores() had wrong and missing {} usage.
|
|
|
|
|
|
|
|
|
|
|
| |
Using results from
J. Sorenson and J. Webster, Strong pseudoprimes to twelve prime
bases, Math. Comp. 86(304):985-1003, 2017.
teach primes(6) to enumerate primes up to 2^64 - 1. Until Sorenson
and Webster's paper, we did not know how many strong speudoprime tests
were required when testing alleged primes between 3825123056546413051
and 2^64 - 1.
Adapted from: FreeBSD
|
|
|
|
|
| |
This allows us to use `wtf is` and get information for the acronym "is"
and produces the same output as `wtf is is` withough requiring the extra
typing by the user.
|
|
|
| |
-d (decode) option works just fine with dashes. :)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This quote is a longer form of "the dogs bark, but the caravan goes on"
and compares Poles and Lithuanians (historical meanings used from the time
of country union of both nations).
Today is the 150th birthday anniversary of Jozef Pilsudski (1867-1935).
|
| |
|
|
|
| |
PR bin/52735
|
| |
|
|
|
| |
"human-readable" form of x^n.
|
|
|
| |
system headers.
|
| |
|
| |
|
|
|
|
| |
seriously: also permit games that contain underscores to be invoked
via wargames(6))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.
In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.
The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.
My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.
As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:
https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html
P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.
|
| |
|
|
|
|
|
| |
The original content is not accessible with the original link (missing
closing /). This page does not look to be updated since 2002 and artwork
is not freely reusable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Stanislaw Lem -> Stanislaw J. Lec
|
|
|
|
|
| |
Pointed out by Antoni GrzymaĆa <antoni@grzymala.info>
This mistake was in the sources since the beginning of this file in NetBSD.
|