Tag Info

Hot answers tagged

3

Since you're going to shut down the servers, boot one of them with a live CD/USB key, mount the root filesystem and chroot into it. Then change the root password and check if there are other users presents and change their password too. Then you can reboot it, connect to the network and procede with the same procedure with the other server.


2

No need to boot up with a live cd as suggested by @Mr Shunz, since the system is working. Just restart the server, in the boot manager select to edit the boot parameters and add an 1 to the end. The system will boot in runlevel 1 with no network and the root user already logged in. Eventually disable system management programs from starting up automatically ...


2

This is how I would do: First I would consider the system compromised. This means I would not trust the data, configs, etc unless is carefully checked. I would prepare a live CD and an empty HDD (can be an uncompromised network storage) I would reset the system (not system reboot, but reset button) and I would make an image of the disk. This image should ...


2

Probably you ask how to prevent hotlinking? Nginx has built in functionality to do that: http://nginx.org/en/docs/http/ngx_http_referer_module.html See an example below: valid_referers none blocked server_names *.example.com example.* www.example.org/galleries/ ~\.google\.; if ($invalid_referer) { return 301 ...


1

Limit access to a relay server that requires authentication and configure the auth data into your Jenkins instance.


1

This answer will depend on using Grub and rebooting the server, but since they're Redhat servers, Grub is practically guaranteed, and it is a sure way to regain access without booting to another medium. Here goes: Initiate a reboot. When the bootloader screen pops up, spam the Escape key to stop automatically booting to the fefault kernel. Using the arrow ...


1

If you're not going to use the interface why not disable it (or not start it) ? You don't say which distro you are using but they should all have a way of not starting an interface when the system boots. For RHEL/CentOS etc you can set ONBOOT=no in the relevant file in /etc/sysconfig/network-scripts For Debian/Ubuntu etc you can set iface InterfaceName ...


1

The answer to your question is no, there is no way within ssh to enforce regular changing pass phrases. As you're using a single account presumably all the public keys will be in a single authorised_keys file so you could invalidate keys by removing them from it. This though feels like too much effort and people could just use the same pass phrase on a ...


1

I think it is reasonable to expect that any system that touches data needs to be encrypted, simply because it is not just the storage of the data that needs to be protected, but also the access. Here are some resources for telecommuting and home offices regarding HIPAA: http://www.all-things-medical-billing.com/hipaa-compliance-and-the-home-office.html ...


1

The following is the law and will be a dry read. http://www.hhs.gov/ocr/privacy/hipaa/understanding/coveredentities/hitechrfi.pdf As I understand the law doesn't require you to implement any specific system but rather requires the system to anticipate and protect the privacy of medical information. It is on the you to interpret what it means to protect the ...



Only top voted, non community-wiki answers of a minimum length are eligible