ownCloud Routing
-
@alex.olynyk said:
and add that name to trusted domains?
You can do that, not normally needed, but it might be in your case.
-
@DustinB3403 said:
Damn....... !!! Scott's ripping on someone
Using "not fixing something simple as an excuse to turn off security" could be classified as a form of social engineering and is very serious.
-
Oh I agree, just the response was very strongly worded.
-
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
-
Once you have the hostname set up you can handle things in a few different ways...
Externally you need to make a DNS entry (A record) for the new server and point to the public IP address of the server. That must be done. Once that is done, external will just work. Internal might but it sounds unlikely.
Internally you can do something as simple as putting that server into the hosts files on the individual machines. A pain, but simple and it works.
You can put a DNS entry in for it internally on your internal DNS. This works better.
-
@DustinB3403 said:
@scottalanmiller said:
If you were to be audited for this, a good auditor would use the term "professional negligence." That means an error so large that puts the business at risk and so inappropriate that a judge would consider lifting employee protections so that the company can prosecute criminal action against the person who did it. This is a level of security blunder so great that your boss has the responsibility to go to management and tell them that he's not qualified to be doing what he is doing and is in over his head to a point where he is a danger to the business. Not doing so puts him in deep legal hot water.
Damn....... !!! Scott's ripping on someone
I think @JaredBusch said it appropriately in the last thread. @alex-olynyk and their boss need to get an MSP or someone in to fix this mess before it does any serious harm, if it hasn't already, to the company.
-
@coliver said:
@DustinB3403 said:
@scottalanmiller said:
If you were to be audited for this, a good auditor would use the term "professional negligence." That means an error so large that puts the business at risk and so inappropriate that a judge would consider lifting employee protections so that the company can prosecute criminal action against the person who did it. This is a level of security blunder so great that your boss has the responsibility to go to management and tell them that he's not qualified to be doing what he is doing and is in over his head to a point where he is a danger to the business. Not doing so puts him in deep legal hot water.
Damn....... !!! Scott's ripping on someone
I think @JaredBusch said it appropriately in the last thread. @alex-olynyk and their boss need to get an MSP or someone in to fix this mess before it does any serious harm, if it hasn't already, to the company.
they are doing this now
-
I missed that thread, I think. Was that also about ownCloud?
-
-
-
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
-
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
By default /etc/httpd/httpd.conf
-
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
I think the settings are in /etc/httpd/conf/httpd.conf.
-
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
-
-
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Thats what we are using
-
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Also it should be someone that you pay explicitly for this service... not on top of other services. I think @scottalanmiller has an article about getting advice from a vendor somewhere.
-
@coliver said:
@scottalanmiller said:
Just to be clear, for your MSP process, it's not a traditional MSP that you want but a consultant. You want someone who will oversee your processes, not just someone who can outsource desktop work.
Also it should be someone that you pay explicitly for this service... not on top of other services. I think @scottalanmiller has an article about getting advice from a vendor somewhere.
Yes, the important thing is that they are not a reseller with product to push.
-
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
I have httpd.conf opened and am searching it for virtualhost:80 and virtualhost:443 but I dont see these directives. Do I have to add them first?
-
@alex.olynyk said:
@alex.olynyk said:
@coliver said:
@alex.olynyk said:
What steps do i need to take to access it by hostname?
If you're using apache (I will assume you are) you need to edit your virtualhost:80 and virtualhost:443 to have the ServerName be owncloud.mycompany.com.
where are these files?
I have httpd.conf opened and am searching it for virtualhost:80 and virtualhost:443 but I dont see these directives. Do I have to add them first?
It should look like:
<Virtualhost *:80>
as the opening line. It is a block of code with defined flags below it.