installing_lucy_on_linux
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
installing_lucy_on_linux [2017/01/30 16:53] – [Uninstall LUCY] lucy | installing_lucy_on_linux [2020/11/17 17:09] – [What if I ran the install.sh on Red Hat without manually installing Docker?] lucy | ||
---|---|---|---|
Line 26: | Line 26: | ||
===== Can LUCY be installed on older Linux Kernel Version (< 3.10)? ===== | ===== Can LUCY be installed on older Linux Kernel Version (< 3.10)? ===== | ||
- | The older versions of the linux setup script (< 2.8) have been tested on Debian 7 (Wheezy), Debian 8 (Jessie), Ubuntu 12.04 and Ubuntu 14.04. As an additional requirement, | + | The older versions of the linux setup script (< Lucy 3.7) have been tested on Debian 7 (Wheezy), Debian 8 (Jessie), Ubuntu 12.04 and Ubuntu 14.04. As an additional requirement, |
Line 34: | Line 34: | ||
* **Make sure you use an updated list of repositories**: | * **Make sure you use an updated list of repositories**: | ||
* **Make sure you have the latest PEM files**: Run " | * **Make sure you have the latest PEM files**: Run " | ||
- | * **Make sure you have enough disk space in your temp drive**: Free some space by using " | + | * **Make sure you have enough disk space in your temp drive**: Free some space by using " |
Line 49: | Line 49: | ||
* openssl | * openssl | ||
* ca-certificates | * ca-certificates | ||
+ | * net-tools | ||
===== What are the hardware/ | ===== What are the hardware/ | ||
- | * TMP: You will need at least 1 GB Space in the tmp directory. Please | + | * TMP: You will need at least 2 GB Space in the tmp directory. Please |
* Other hardware requirements can be found [[hardware|here]] | * Other hardware requirements can be found [[hardware|here]] | ||
Line 59: | Line 60: | ||
===== Installation tutorial ===== | ===== Installation tutorial ===== | ||
- | 1) First of all, download the file that you are going to execute e.g. " | + | **Important notice:** |
+ | If you use a Red Hat Linux, before running the LUCY installation script, please deploy Docker manually.\\ | ||
+ | [[https:// | ||
+ | |||
+ | |||
+ | 1) First of all, download the file that you are going to execute e.g. " | ||
2) Secondly, open the Terminal from Menu " | 2) Secondly, open the Terminal from Menu " | ||
3) Now type cd to the directory where you downloaded the file.\\ | 3) Now type cd to the directory where you downloaded the file.\\ | ||
4) Then type chmod +x name_of_file.sh to make your file executable (example " | 4) Then type chmod +x name_of_file.sh to make your file executable (example " | ||
- | 5) Now type ./ | + | 5) Now type ./ |
- | 6) You will be asked if you want to install LUCY (Install LUCY (y/n)?) Please type " | + | 6) You will be asked if you want to install LUCY (Install LUCY (y/n)?) Please type " |
7) As soon as the installation is finished, the [[setup_script_tutorial|automatic setup script]] should start. | 7) As soon as the installation is finished, the [[setup_script_tutorial|automatic setup script]] should start. | ||
{{ 97.jpg?600 }} | {{ 97.jpg?600 }} | ||
+ | |||
+ | 8) [[lucy_weblogin|Login]] to LUCY with the Webbrowser. Continue the setup in the browser using the credentials provided in the setup script. If you want to install a commercial version, please provide us with the [[how_to_activate_lucy|workstation ID]]. | ||
+ | |||
+ | 9) Define your [[mail_delivery_methods_in_lucy|default mail delivery method]] in LUCY. In case you use the build in mail server: set the [[set_hostname_for_smtp_communication|hostname]] for the mail server. | ||
+ | |||
+ | 10) Setup a [[domain_configuration|domain]] in LUCY. This domain can be used for phishing simulations (landing pages) or the elearning portal. | ||
+ | |||
+ | 11) Create a [[ssl_configuration|trusted certificate]] for the administration of LUCY. | ||
+ | |||
+ | 12) Create all the required administrators [[user_management|users]] in LUCY. | ||
+ | |||
+ | 13) [[download_templates|Download]] all the latest templates | ||
+ | |||
+ | 14) [[update_lucy|Update]] LUCY to the latest version | ||
+ | |||
+ | 15) Consider implementing additional [[security_considerations|security layers]] | ||
+ | |||
+ | 16) Give LUCY a [[white_label_lucy_-_custom_branding|custom branding]] | ||
+ | |||
+ | 17) Once you are all set you can try to [[create_your_first_phishing_campaign|setup your first campaign]]. If you experience issues with mail delivery (e.g. SPAM filtering), check out [[avoid_spam_issues|this]] chapter. If your test emails do not arrive at all, please consult [[mail_communication_issues: | ||
===== Start the installation script manually after a successful installation ===== | ===== Start the installation script manually after a successful installation ===== | ||
- | Execute the command | + | Execute the command |
+ | **python / | ||
+ | |||
+ | or in LUCY > 2.8: \\ | ||
+ | **docker exec -it lucy /bin/bash** \\ | ||
+ | **python / | ||
+ | |||
+ | |||
+ | |||
+ | ===== Installation problem? Contact our support ===== | ||
+ | In case you are planning | ||
===== Uninstall LUCY ===== | ===== Uninstall LUCY ===== | ||
- | In 3.2 we will provide an uninstaller. For now if you want to remove LUCY you first need to get a list of all packages installed using $awk '/ | + | |
+ | If you want to remove LUCY you first need to get a list of all packages installed using the command (which displays installed packages in historical order, and then purges the last packages): | ||
+ | < | ||
+ | awk '/ | ||
+ | </ | ||
+ | |||
+ | That list will enable you to remove the according packages. This method works for legacy installation method only. | ||
+ | |||
+ | For Docker-based installation you simply need to stop the container and remove it: | ||
+ | |||
+ | < | ||
+ | docker stop lucy | ||
+ | docker ps -a | ||
+ | docker container rm < | ||
+ | </ | ||
+ | ====== Frequently asked questions | ||
+ | ===== Which components are installed | ||
+ | When Lucy is installed as a docker image, it gets downloaded from https:// | ||
+ | |||
+ | When installing Lucy in a " | ||
+ | |||
+ | In case if you use Red Hat, please look at the important notice in the Installation tutorial section. | ||
+ | |||
+ | ===== What if I ran the install.sh on Red Hat without manually installing Docker? ===== | ||
+ | Our installation script actually does not deploy Docker itself. \\ | ||
+ | It pulls Docker Installation script from https:// | ||
+ | For some reason, Docker installation script adds a repo which is not operational. \\ | ||
+ | To remove the repo, simply run the command below: \\ | ||
+ | // | ||
+ | |||
+ | ===== The installer checks if docker is installed and installs it from the official docker website. Are there any downsides of having docker engine pre-installed? | ||
+ | No, pre-installed docker engine is just fine and will work completely the same. Just make sure it will be updated on time. | ||
+ | |||
+ | |||
+ | ===== Who patches the Docker Runtime and host Linux system when security vulnerabilities become known? ===== | ||
+ | When using a Docker-based installation, | ||
+ | When using a " | ||
+ | |||
+ | |||
+ | ===== How does Lucy update when it’s running in Docker? ===== | ||
+ | After installing a Docker container with Lucy, Docker' | ||
+ | |||
+ | |||
+ | ===== Is the docker-image included in the installer payload or is the docker-image loaded via docker pull? ===== | ||
+ | Lucy's docker-image gets downloaded from https:// | ||
+ | |||
+ | |||
+ | ===== When configuring proxy in Lucy, what software is affected? ===== | ||
+ | In case of Docker installation, | ||
+ | When using a legacy installer, the proxy configured will be used as a default proxy for the whole Linux system. | ||
+ | |||
+ | |||
+ | ===== How do you back up Lucy? ===== | ||
+ | Speaking of Docker container installation, | ||
+ | **docker commit lucy lucy-backup** | ||
+ | After that you: | ||
+ | * either save it as a tar file: **docker save -o / | ||
+ | * or export it to your private docker registry: **docker push lucy-backup** | ||
+ | |||
+ | The backup image can be recovered easily from file by **docker load -I / | ||
+ | |||
+ | After that you can start your container as a regular docker container with this command: | ||
+ | **docker run --privileged -v / | ||
+ | |||
+ | Things get a bit more difficult in case of " | ||
+ | * / | ||
+ | * /etc/ | ||
+ | * /var/lib | ||
installing_lucy_on_linux.txt · Last modified: 2022/06/22 12:37 by lucysecurity