Closed
Bug 181016
Opened 23 years ago
Closed 22 years ago
selfserv doesn't run on OS/2
Categories
(NSS :: Tools, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: julien.pierre, Assigned: wtc)
Details
Attachments
(1 file)
|
1.64 KB,
patch
|
Details | Diff | Splinter Review |
When building NSS standalone, the SSL server selfserv runs but fails in
PR_SetFDInheritable. This function is not supported on OS/2.
| Reporter | ||
Comment 1•23 years ago
|
||
Comment 2•23 years ago
|
||
Shouldn't we just make PR_SetFDInheritable return success so code doesn't have
to change?
If it is not really needed?
| Reporter | ||
Comment 3•23 years ago
|
||
No, this is usually done for a good reason - security. Those sockets really
shouldn't be accessible to the child processes. In a web server for example that
would mean a CGI program could "steal" connections from the main daemon. This
disalbing is only OK to do it in the example server program because it isn't a
real server program, I only use it for performance testing. But serious
applications might be calling the function and tricked into thinking that it
works. We don't want to happen.
Incidently, perhaps there is actually way to enable/disable the sharing of the
sockets on OS/2 ? I don't know how, but if you know anyone who worked on TCP/IP
for OS/2, it's worth asking.
Comment 4•23 years ago
|
||
Seems like this is really a bug against NSPR on OS/2.
NSS code is doing the correct thing.
I'm inclined to mark this invalid. Objections?
Priority: -- → P3
Comment 5•22 years ago
|
||
The bug is that PR_SetFDInheritable doesn't work. We don't need two bugs.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 6•22 years ago
|
||
You can also make selfserv do something sensible if
PR_SetFDInheritable fails with PR_NOT_IMPLEMENTED_ERROR.
But I have no problem with marking this bug invalid or
WONTFIX.
You need to log in
before you can comment on or make changes to this bug.
Description
•