Note: Please always verify that you run the latest LUCY version. Bug fixes are not included in the security patches - only within the regular updates, which are available for commercial clients. Community Edition Users therefore need to make sure, that they first download the latest version!
Always make sure you are running the latest version of LUCY by checking if there are any updates available. If updating the system via HTTP does not work: download the latest version from the internet.
Please define your time zone within the settings menu.
Within the settings menu you can specify a proxy server together with the port and login credentials. LUCY will use those settings to connect to the internet.
If you experience mail issues we recommend first checking the error log within your campaign:
There are many reasons for mail communication errors. Example: In LUCY mails appeared to be send to your recipients. But mails never arrived or arrived very late. There a few issues to check:
To make sure mails arrive we recommend defining a test mail recipient and conducting a test run. If the mail does not arrive you can contact us and we will help you.
This is usually not caused by LUCY. If we cannot establish a SMTP connection we won’t retry for many hours. This is easy to verify: LUCY tells you if all mails have been send. Usually this is done within seconds or minutes and can also be tracked with Wireshark or similar tools. So if all mails have been sent then technically there is nothing left for LUCY to do to accelerate delivery. So in over 95% of cases the process of delivery takes less than a minute. In a few cases the message could take as long as 5 days to complete its trip from sender to recipient. It rarely takes more than 5 days, as one of the SMTP servers will send the message back as undeliverable. And yes, the e-mail that contains the error message could take 5 days to get back! You also have to remember that there is a lot of software and hardware in between that your email has to pass through to get from the point of origin to its destination. Whether is server hardware, software, routers, switches, copper or fiber optic cables, power grids, or even your own computer, there are many potential points of failure along the way. If any one of these has an outage or is overloaded, a delay can occur.
It is very unlikely that the file is classified as a virus since we don’t simulate any virus behaviors (we don’t do any changes on the system). But we noticed that certain vendors have a category like “suspicious. insight” or “unknown”. Basically it gets classified comes from an unknown source and there is no record of this file in the internet. As a result any unknown software would be put in this category.
To solve this you simply need to stop the campaign, delete the recipient group, then add the same recipient group again and start the campaign again.
Opposite to the phishing website the awareness website has to be started manually in order to work (has to be published and started). Sometimes the automatic sending of the awareness site also depends, if LUCY has recorded an successful attack. This depends on the scenario type. Example: if you create a file based campaign and then use a data entry template LUCY won’t consider the login from the user as a “success”. Only the file download from a user would be a “success” and start the automatic awareness mail.
You might not allow direct access to the internet via a web browser. Instead you might allow access to the internet using a physical different PC or a different infrastructure (e.g. accessing the internet via Citrix etc.). As a result a link sent in a mail can’t be opened). The only way to conduct a phishing attack in such an environment without having the user to type a long randomized URL into a different system is by setting a directory within the URL manually. This can be done within the recipient file. There is a variable which you can set called “Link” – a unique link part for the landing page. If you specify this, please make sure it is unique across all recipients in the scenario and does not contain any special characters. If you skip this, the link will be generated automatically. You can choose a simple name for a link for a group of recipients (keep in mind that you can upload different recipient groups per scenario). Recipient group 1 could look like this:
Recipient group 2 could look like this:
The user from Recipient group 1 would then receive a link to your campaign which he can remember easily (and therefore manually type in a different browser) like http://your.phishing-domain.com/USA. The user from Recipient group 2 would get a link like http://your.phishing-domain.com/Switzerland.
LUCY can run without any internet connection. But there are certain scenarios where an internet connection might be required:
If you’re using Debian 7 and installing the software through the shell script, then you might need to reboot the system for Spam Assassin to start. It may fail to start automatically sometimes - that’s why the Spam Check may hang. That behavior has been fixed in 2.2. In LUCY 2.2-2.5 the SPAM check will verify over 200 online DB's. This takes at least 10-15 minutes for this check to be finished! Starting from 2.6 the SPAM check is optional and not enabled by default.