03-23-2009
Do a grep through all your apache conf files for the name of the old crt file, to see where it references that file. You may have to do it recursively, if the previous guy created a subdirectory and included a conf file from there.
The alternative lazy way: you can rename your three files and replace the previous guy's files with yours, and then take your modifications out of the conf file.
9 More Discussions You Might Find Interesting
1. Web Development
Dear All
Anyone know how to issue two different certification on apache virtualhost fyi i have one virtualhost eg 69.192.1.25:443 already signed with verisign how can i configure another virtualhost 69.192.1.25:443 which signing with another certificate which self signing. i search net not... (1 Reply)
Discussion started by: netxus
1 Replies
2. AIX
Hello,
I am new in UNIX, and some one asks me to install SSL certificates to allow exchange with an external system.
Can someone tell how to install certificate (ex : verisignxxx.cer) on a UNIX server?
Many thanks.
Tibo (4 Replies)
Discussion started by: tibo51
4 Replies
3. Cybersecurity
Hi guys.
I have some questions about ssl certificates.
I looked at SSL providers and saw that they are providing 2 types of certificates: per server or per domain.
my server host name is: srv1.example.com
I have a smtp, imap, web server on this box. but all services accessed by different... (1 Reply)
Discussion started by: majid.merkava
1 Replies
4. Web Development
we are doing TCP for our systems. I have a working SSL certificate on prodction webserver. Im planning to export it to our DR server for TCP purposes. However when I export based on the procedure below, it doesn't work. When I restart the DR webserver, it still says the certifcate is expired.Any... (1 Reply)
Discussion started by: lhareigh890
1 Replies
5. Red Hat
Hi,
I want to renew the ssl certificate for one of my application on tomcat without down time. I want to know what would the possible impacts for the users who currently have sessions to the app.
Regards,
Arumon (1 Reply)
Discussion started by: arumon
1 Replies
6. Web Development
Hi,
I was trying to enable SSL cert on WebLogic 10.3 (CentOS),
I don't have a third party Certificate Authority(C.A) to get the .csr file certified.
Is there an alternate way that replaces the step sending .csr file to CA ?
Thanks
SZS (1 Reply)
Discussion started by: szs
1 Replies
7. Red Hat
Hi guys,
I'm trying to generate a key using the genkey command in centos 6.4 and RHEL6.4, Every thing seems to go cool but I get this error message bad certificate request error -8016 and no key/cert is generated. I don't want use the many openssl(s) commands instead since genkey is a shourtcut... (4 Replies)
Discussion started by: leo_ultra_leo
4 Replies
8. Cybersecurity
Hey everyone, I'm trying to get a lay of the land for OS and Application Certificate Stores. Can someone confirm that I have this concept right?
If the application you're using say Firefox has it's own trusted CA store, it uses that exclusively. So if you're running firefox in Windows, Firefox... (4 Replies)
Discussion started by: Lost in Cyberia
4 Replies
9. Web Development
Hello!
I had a cron job running on my website, activating a php script every friday. The Php script just activated another photo to add in the gallery. It worked fine until I got an SSL certificate for my website, then everything broke.
This was the command before:
lynx -source... (0 Replies)
Discussion started by: AGDesign
0 Replies
LEARN ABOUT DEBIAN
innupgrade
INNUPGRADE(8) InterNetNews Documentation INNUPGRADE(8)
NAME
innupgrade - Upgrade INN configuration files
SYNOPSIS
innupgrade directory
innupgrade [-t type] -f file
DESCRIPTION
innupgrade is intended to be run during a major upgrade of INN to fix the configuration files with any required changes. If given a
directory, it will scan that directory for any files that it has updates defined for, try to perform those updates, and replace the files
with updated versions if applying the updates resulted in any changes. The old versions of the files will be saved with a ".OLD"
extension.
If the -f flag is used, only that file will be updated. If the file name doesn't match the standard file name of an INN configuration
file, the optional -t flag may be given to specify the type. See "EXAMPLES" for an example of this.
Currently, innupgrade knows how to apply the following updates:
inn.conf
o Quote values with whitespace and comment out keys with no values, required for the change in configuration parsers introduced in
INN 2.4. The new format is not backward compatible with the previous parser, since the previous parser will include the double-quotes
in the value of the parameter.
o Add the hismethod parameter if not found (introduced in INN 2.4, with the default value "hisv6") and rename nntpactsync to
incominglogfrequency (since INN 2.5).
o If the overview.fmt file exists, its content is merged in the extraoverviewadvertised and extraoverviewhidden parameters introduced in
INN 2.5. The file is then renamed to overview.fmt.OLD.
o If the sasl.conf file exists, its content is merged in the tlscapath, tlscafile, tlscertfile and tlskeyfile parameters introduced in
INN 2.5. The file is then renamed to sasl.conf.OLD.
newsfeeds
o Replace the use of startinnfeed with the appropriate direct invocation of innfeed or imapfeed.
A few obsolete programs or configuration files are renamed with a ".OLD" extension by innupgrade. Obsolete man pages are directly removed.
Normally, innupgrade should be run at least on the pathetc directory after any upgrade of INN other than a patch release (any upgrade that
changes the first or second version numbers). This may occur automatically during the upgrade process.
OPTIONS
-f file
Only act on file rather than working on an entire directory.
-t type
For a file specified with -f, parse it and upgrade it as if it were named type. Used for upgrading files with the same syntax as
normal INN configuration files but with different names. Only makes sense in combination with -f.
EXAMPLES
Upgrade any configuration files found in pathetc and append a ".OLD" extension to obsolete files in pathetc:
innupgrade <pathetc in inn.conf>
Upgrade only /news/etc/inn.conf:
innupgrade -f /news/etc/inn.conf
Upgrade a file named inn-special.conf that should have the same syntax as inn.conf:
innupgrade -t inn.conf -f inn-special.conf
Any upgrade rules that apply to inn.conf will be applied to the alternate file.
HISTORY
Written by Russ Allbery <rra@stanford.edu> for InterNetNews.
$Id: innupgrade.pod 8415 2009-04-12 20:19:35Z iulius $
INN 2.5.3 2009-05-21 INNUPGRADE(8)