Bug 1254032

Summary: 8.1.1 advice on using getpid to avoid fork problems is dangerously wrong
Product: [Fedora] Fedora Documentation Reporter: Steven Stewart-Gallus <sstewartgallus00>
Component: defensive-coding-guideAssignee: Florian Weimer <fweimer>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 15:29:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steven Stewart-Gallus 2015-08-17 00:22:22 UTC 
Description of problem:

If one forks a process, the original process dies and then the second one forks again the last forked process can have the same pid as the original and so getpid will not detect a change.  This was a widely noted weakness in LibreSSL (see https://www.agwa.name/blog/post/libressls_prng_is_unsafe_on_linux.)

How reproducible:

This is very probably systematically reproducible in possibly affected libraries but in practise should never really happen.
Comment 1 Petr Bokoc 2019-11-07 15:29:54 UTC 
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.