Re: [users@httpd] better configtest
> What is the point of not starting httpd if there is an issue with a single > virtual host? This gives the best feedback to the user that the config couldn't be honored. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
RE: [users@httpd] better configtest
> > > > 1. > > what is the point of having a apachectl configtest, when a restart can > still fail? It can't be to difficult to include cert checks here, can it? > This is now becoming a significant part. > > The bar is useful, not perfect. configtest checks for _syntax_ validity. > > > 2. > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > AH00016: Configuration Failed > > > > This is useless, why not list config line or cert name? > > This error means post-configuration failed. This is when the collected > config is acted upon, which is not really within line-by-line mode. > Normally there's a preceding error message with more details, maybe in > a vhost-specific error log? Maybe, I would have to look through quite a lot. Can't the development team re-think about this? What is the point of not starting httpd if there is an issue with a single virtual host? Why not have that specific virtual host fail only? I would like to have this config syntax check expanded to cert content or some other way of validating that I can test if I can restart httpd safely. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
On Wed, Apr 17, 2024, 3:27 PM General Email < general.email.12341...@gmail.com> wrote: > > >> > If people are asking for advice on PHP then advise them on PHP or don't >> say anything. >> > Don't start advising them about Java. >> >> Please... I am not even making remarks about you asking openssl questions >> at httpd. >> > > > So, is this wrong forum for asking about openssl commands required for > generating certificates for enabling https on apache? > > I can easily look at openssl website or other websites and look how to > create self signed certificates. However, I was not sure if that would work > on apache. That's why I asked here. > > Most of the websites showed how to generate .pem certificates, but after > reading about ssl/https on apache website, I saw that apache requires .crt > certificates. > > Obviously, I can figure out this whole thing if I read whole openssl > manual and apache ssl configs, etc. but I don't want to invest time in that > and I was looking for a quick solution and that's why I posted here. > > > >> I think most people will understand that I try to make you see the >> difference between developing an application and how it is hosted/used what >> ever, operate within your area of expertise. >> > > I know this and I told you that I want to hard code https. Now, please > tell me how can my idea go wrong? > > Please don't tell me how other people's unrelated ideas went wrong. > > Let's have a meaningful discussion. > > I don't work for any company. > > I do freelancing. I am doing this project for a real estate client. So, > its only me who will do everything and decide everything - development, > testing, maintenance hosting, hard coding, migration, https, ssl, etc. > > I would really like to know how my idea of hardcoding https can go wrong? > Anyways, I looked more on google and I think that I have found what I was looking for on this page: https://gist.github.com/taoyuan/39d9bc24bafc8cc45663683eae36eb1a
RE: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
> > So, is this wrong forum for asking about openssl commands required > for generating certificates for enabling https on apache? > Mostly you will be notified. The only thing you need to add to your virtual host for https is this: SSLEngine on SSLCertificateFile SSLCertificateChainFile SSLCertificateKeyFile It really does not matter how keys / crts have been generated. Just choose something that is quick and easy. > > Most of the websites showed how to generate .pem certificates, but > after reading about ssl/https on apache website, I saw that apache > requires .crt certificates. pem, crt, cer check if they start like this -BEGIN CERTIFICATE- check apache log file for start up errors. > Obviously, I can figure out this whole thing if I read whole > openssl manual and apache ssl configs, etc. but I don't want to invest > time in that and I was looking for a quick solution and that's why I > posted here. > Just choose a tool that can quickly generate key and crt. Does not matter which tool. Someone send you already reply to something. > I would really like to know how my idea of hardcoding https can go > wrong? > It can be anything, it is just unexpected application behaviour to someone who might work with it in the future. Maybe internal health check url? Cron? Debugging? Personally I find it sometimes annoying with testing container images. In my own development environment I am constantly switching between development and production certs. I would always opt for having this at least configured as an option. > > Anyways, I looked more on google and I think that I have found what I was > looking for on this page: > https://gist.github.com/taoyuan/39d9bc24bafc8cc45663683eae36eb1a > Forget about going specific for openssl, it is just a tool. Choose the simplest solution for your development environment. If you are doing hosting yourself. Your going to end up with automated certs on your hosting environment any way, you will never see an openssl command.
RE: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
> I don't know what you are trying to prove by your points + you are > insulting people for no reason. I am insulting no one, mostly stating what is common. > If you insult people, they may insult you back. > > Russia attacked Ukraine and Ukraine/NATO hit Russia back. I think you are the only one on this planet that would dare to summarize this conflict like this. But it proves my point, stick just to what you know, with development. > The original discussion was about openssl commands and I think that since > you don't know openssl commands, you should not have said anything. > You wrote it was for a local development environment. I just thought why bother with the openssl? Obviously I should not have made assumptions. You could also be cryptographer working on mod_ssl. > Let other people do what they want to do. If they want to hardcode > something, why are you bothered. I am just pointing out there multiple roads that lead to Rome. Some of which are known to be less troublesome than others. If you get stuck on some dirt track to Rome, others will be required to come and help. > I will hard code https, its my choice. It has nothing to do with you. > Obviously, I am just stating it is not really what most experienced professionals do. > Now, you are saying to hard code root name servers, etc. which doesn't > make sense. Because you do not know about it. That is the point I am trying to make. Just separate it from application development. > You are taking this discussion in all sorts of directions and I don't > know what you want to prove. Really? I thought I made my point numerous times. > If people are asking for advice on PHP then advise them on PHP or don't say > anything. > Don't start advising them about Java. Please... I am not even making remarks about you asking openssl questions at httpd. > > By the way, if you insult me, I will insult you back. > I think most people will understand that I try to make you see the difference between developing an application and how it is hosted/used what ever, operate within your area of expertise.
Re: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
> > > If people are asking for advice on PHP then advise them on PHP or don't > say anything. > > Don't start advising them about Java. > > Please... I am not even making remarks about you asking openssl questions > at httpd. > So, is this wrong forum for asking about openssl commands required for generating certificates for enabling https on apache? I can easily look at openssl website or other websites and look how to create self signed certificates. However, I was not sure if that would work on apache. That's why I asked here. Most of the websites showed how to generate .pem certificates, but after reading about ssl/https on apache website, I saw that apache requires .crt certificates. Obviously, I can figure out this whole thing if I read whole openssl manual and apache ssl configs, etc. but I don't want to invest time in that and I was looking for a quick solution and that's why I posted here. > I think most people will understand that I try to make you see the > difference between developing an application and how it is hosted/used what > ever, operate within your area of expertise. > I know this and I told you that I want to hard code https. Now, please tell me how can my idea go wrong? Please don't tell me how other people's unrelated ideas went wrong. Let's have a meaningful discussion. I don't work for any company. I do freelancing. I am doing this project for a real estate client. So, its only me who will do everything and decide everything - development, testing, maintenance hosting, hard coding, migration, https, ssl, etc. I would really like to know how my idea of hardcoding https can go wrong?
Re: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
On Wed, Apr 17, 2024, 1:17 PM Marc wrote: > > > > > http is an insecure protocol. I don't want my website to run on > > http. So, I am hardcoding https in links in my website that refer to > > pages in my website. > > > > > > Now, I know that you will write why not redirect http to https by > > default. > > No because that is not relevant to me and what I would like to address. I > am even deploying https on tasks in private air-gapped environments. This > is not a discussion about whether or not https should be used and when. > > > > The problem with this is that if the website gets migrated to > > different provider and if people forget to redirect http to https in new > > setup then it will become a security problem. > > I know there are many idiots out there and your concern is very valid. > Most of the security breaches you read about is about such issues. > However, can you imagine the apache dev team thinking like you? Hard > coding everything to https? Can you imagine all http ports of tomcat, > httpd, jboss etc. being dropped? These people have been making rock solid > applications for decades they don't lecture others how to use or not use > https. > You will never match them in any way, why not follow their lead? > > > > Hardcoding https solves all issues. > > > > A few years back I had an argument with apple developers. They were having > in the build process of the calendar server openssl. The developers thought > for security purposes it would be better to include it in the build. This > resulted in that calenderservers were always having an old insecure > openssl, because the openssl updated by the distribution was not used. (and > nobody is going to build the application frequently) This is what happens > when application developers think they are security geniuses. > > The point I am trying to make is that you as an application developer > should be focussed on developing your application it is not your business > how this application is hosted. You should not concern yourself with things > you are not experienced in/with. Especially when it comes to something as > crucial as security. You are not removing ca certs from the trust store, > your are not setting secure ciphers, you are not setting limits on key > sizes etc. Why would you then even bother with https or http? > > With your argument you might as well hard code the domain name in your > application (like wordpress) and hardcode root name servers etc. > If you buy an egg in the store, it does not come with any requirement that > it should be used only for making cakes. Grasp this concept. > Marc, I don't know what you are trying to prove by your points + you are insulting people for no reason. If you insult people, they may insult you back. Russia attacked Ukraine and Ukraine/NATO hit Russia back. The original discussion was about openssl commands and I think that since you don't know openssl commands, you should not have said anything. Let other people do what they want to do. If they want to hardcode something, why are you bothered. I will hard code https, its my choice. It has nothing to do with you. Now, you are saying to hard code root name servers, etc. which doesn't make sense. You are taking this discussion in all sorts of directions and I don't know what you want to prove. If you want to prove that you are a very smart person and other people are fools then for that you need to play chess with all other people and win all the games. You can invite wordpress idiots to play chess with you and then if you win then probably you can tell that person that he/she is an idiot. There are many people in this world who are very smart but they don't say that other people are fools - for example, Steve Wozniak, Larry Page, Knuth, etc. If people are asking for advice on PHP then advise them on PHP or don't say anything. Don't start advising them about Java. By the way, if you insult me, I will insult you back. GE
RE: [users@httpd] openssl comand(s) for https mode on apache 2.4 on windows.
> > http is an insecure protocol. I don't want my website to run on > http. So, I am hardcoding https in links in my website that refer to > pages in my website. > > > Now, I know that you will write why not redirect http to https by > default. No because that is not relevant to me and what I would like to address. I am even deploying https on tasks in private air-gapped environments. This is not a discussion about whether or not https should be used and when. > The problem with this is that if the website gets migrated to > different provider and if people forget to redirect http to https in new > setup then it will become a security problem. I know there are many idiots out there and your concern is very valid. Most of the security breaches you read about is about such issues. However, can you imagine the apache dev team thinking like you? Hard coding everything to https? Can you imagine all http ports of tomcat, httpd, jboss etc. being dropped? These people have been making rock solid applications for decades they don't lecture others how to use or not use https. You will never match them in any way, why not follow their lead? > Hardcoding https solves all issues. > A few years back I had an argument with apple developers. They were having in the build process of the calendar server openssl. The developers thought for security purposes it would be better to include it in the build. This resulted in that calenderservers were always having an old insecure openssl, because the openssl updated by the distribution was not used. (and nobody is going to build the application frequently) This is what happens when application developers think they are security geniuses. The point I am trying to make is that you as an application developer should be focussed on developing your application it is not your business how this application is hosted. You should not concern yourself with things you are not experienced in/with. Especially when it comes to something as crucial as security. You are not removing ca certs from the trust store, your are not setting secure ciphers, you are not setting limits on key sizes etc. Why would you then even bother with https or http? With your argument you might as well hard code the domain name in your application (like wordpress) and hardcode root name servers etc. If you buy an egg in the store, it does not come with any requirement that it should be used only for making cakes. Grasp this concept. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
