- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Apache's "httpd -DSSL" start PAM'able ?
Operating System - HP-UX
1753776
Members
7153
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2003 02:56 AM
01-20-2003 02:56 AM
Apache's "httpd -DSSL" start PAM'able ?
Hello,
we have a silly configured webserver that is run as an MC/SG package.
The reason for the daft configuration derives from a trust split between customer (who is responsible for web content) and us (who provide the host, infrastructure and systemadministration).
That means we know the root password whereas they know the mantra for the SSL certificate.
This results in a virtually unfit MC/SG application because the package can't be started automatically, for httpd prompts the user to enter his mantra for the SSL certificate.
I suggested the customer to relinquish a mantra altogether when producing the certificate (similar to the empty -N "" option of ssh-keygen when users want to distribute their RSA public keys to ssh servers they wish to login without providing a password).
I told them that otherwise the webserver package couldn't be switched automatically to the failback node.
An empty mantra as well as storing the mantra somewhere on the webserver of course isn't an option for them.
I wonder if the Pluggable Authentication Modules (PAM) - maybe in conjunction with the Secure Remote Password (SRP) protocol - could be the solution to this catch22?
At home on my Linux box I got a little acquainted with the various configuration possibilities of the PAM, but haven't found out yet whether Apache together with openssl is PAM'able.
Is anyone of you conciously using PAM on HP-UX, maybe even with custom authentication schemes for applications that require special treatment in this respect?
How would PAM impact a "HP-trused system" (which we converted this box's passwd to)?
Can you provide me with links, FAQs, Howtos, WhitePapers etc. for PAM on HP-UX?
(seems to be standard on HP-UX meanwhile because I discovered an /etc/pam.conf without being aware of this so far)
we have a silly configured webserver that is run as an MC/SG package.
The reason for the daft configuration derives from a trust split between customer (who is responsible for web content) and us (who provide the host, infrastructure and systemadministration).
That means we know the root password whereas they know the mantra for the SSL certificate.
This results in a virtually unfit MC/SG application because the package can't be started automatically, for httpd prompts the user to enter his mantra for the SSL certificate.
I suggested the customer to relinquish a mantra altogether when producing the certificate (similar to the empty -N "" option of ssh-keygen when users want to distribute their RSA public keys to ssh servers they wish to login without providing a password).
I told them that otherwise the webserver package couldn't be switched automatically to the failback node.
An empty mantra as well as storing the mantra somewhere on the webserver of course isn't an option for them.
I wonder if the Pluggable Authentication Modules (PAM) - maybe in conjunction with the Secure Remote Password (SRP) protocol - could be the solution to this catch22?
At home on my Linux box I got a little acquainted with the various configuration possibilities of the PAM, but haven't found out yet whether Apache together with openssl is PAM'able.
Is anyone of you conciously using PAM on HP-UX, maybe even with custom authentication schemes for applications that require special treatment in this respect?
How would PAM impact a "HP-trused system" (which we converted this box's passwd to)?
Can you provide me with links, FAQs, Howtos, WhitePapers etc. for PAM on HP-UX?
(seems to be standard on HP-UX meanwhile because I discovered an /etc/pam.conf without being aware of this so far)
Madness, thy name is system administration
- Tags:
- Apache
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2003 11:08 AM
01-20-2003 11:08 AM
Re: Apache's "httpd -DSSL" start PAM'able ?
Hello.
I had similar problem with automated apache startup with startssl parameter. Solution provided by Apache.org is to complile RSA certificate without password
# cp -p server.key server.key.orig
# openssl rsa -in server.key.orig -out server.key
and protect it on the OS level i.e. mode 400 owned by bin:bin.
Once this was done, automated startup works.
Hope this helps,
0leg
I had similar problem with automated apache startup with startssl parameter. Solution provided by Apache.org is to complile RSA certificate without password
# cp -p server.key server.key.orig
# openssl rsa -in server.key.orig -out server.key
and protect it on the OS level i.e. mode 400 owned by bin:bin.
Once this was done, automated startup works.
Hope this helps,
0leg
Professionals will prevail ...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP