Correct sense of crypt(3) NULL checks in init(8) and lock(1)
ClosedPublic
Actions

Authored by cem on Oct 2 2017, 11:46 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Fri, Nov 21, 2:25 AM

	Unknown Object (File)
	Fri, Nov 21, 2:24 AM

	Unknown Object (File)
	Fri, Nov 21, 2:22 AM

	Unknown Object (File)
	Fri, Nov 21, 2:19 AM

	Unknown Object (File)
	Oct 25 2025, 10:47 PM

	Unknown Object (File)
	Oct 22 2025, 12:49 AM

	Unknown Object (File)
	Oct 21 2025, 7:43 AM

	Unknown Object (File)
	Oct 20 2025, 8:43 PM

View All 84 Files

Subscribers

None

Details

Reviewers

jhb

Commits

rS324229: Correct sense of crypt(3) NULL checks in init(8) and lock(1)

Summary

In r231994, an attempt was made to fix crypt(3) failure returns (NULL).
However, instead of treating crypt(3) failure as authentication failure,
some of the changes treated crypt(3) failure as authentication success.
This is wrong.

r324225 fixed this for ppp, which also inspired this review. The other
changes in the 231994 revision were audited for correctness and look ok.

Diff Detail

Lint

Lint Passed

Unit

No Test Coverage

Build Status

Buildable 11849
Build 12187: arc lint + arc unit

Event Timeline

cem created this revision.Oct 2 2017, 11:46 PM

jhb accepted this revision.Oct 3 2017, 12:30 AM

This revision is now accepted and ready to land.Oct 3 2017, 12:30 AM

Closed by commit rS324229: Correct sense of crypt(3) NULL checks in init(8) and lock(1) (authored by cem). · Explain WhyOct 3 2017, 12:53 AM

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

sbin/

init/

init.c

2 lines

usr.bin/

lock/

lock.c

2 lines

Diff 33644

View Options

sbin/init/init.c