1.1 --- a/data/dictionary.xml	Wed Jun 24 22:00:50 2020 +0200
     1.2 +++ b/data/dictionary.xml	Mon Jul 06 22:43:15 2020 +0200
     1.3 @@ -2084,6 +2084,64 @@
     1.4  		<tag>computer</tag>
     1.5  	</concept>
     1.6  	<concept>
     1.7 +		<term abbreviation="" completeForm="black list" language="en"/>
     1.8 +		<term abbreviation="" completeForm="black-list" language="en"/>
     1.9 +		<term abbreviation="" completeForm="blacklist" language="en"/>
    1.10 +		<term abbreviation="" completeForm="blacklisting" language="en"/>
    1.11 +		<term abbreviation="" completeForm="blacklisted" language="en"/>
    1.12 +		<explanation language="en">
    1.13 +			<text>
    1.14 +				a list of elements that are not allowed or should be excluded;
    1.15 +				the element might be e.g. IP address, e-mail address, regular expression, name pattern or name;
    1.16 +				example 1: we do not accept e-mail messages from blacklisted IP addresses, because such IP addresses are known to send spam
    1.17 +				example 2: blacklisted kernel modules are not loaded during the system start
    1.18 +			</text>
    1.19 +		</explanation>
    1.20 +		<tag>computer</tag>
    1.21 +		<tag>security</tag>
    1.22 +	</concept>
    1.23 +	<concept>
    1.24 +		<term abbreviation="" completeForm="white list" language="en"/>
    1.25 +		<term abbreviation="" completeForm="white-list" language="en"/>
    1.26 +		<term abbreviation="" completeForm="whitelist" language="en"/>
    1.27 +		<term abbreviation="" completeForm="whitelisting" language="en"/>
    1.28 +		<term abbreviation="" completeForm="whitelisted" language="en"/>
    1.29 +		<explanation language="en">
    1.30 +			<text>
    1.31 +				a list of elements that are allowed or should be included;
    1.32 +				the element might be e.g. IP address, e-mail address, regular expression, name pattern or name;
    1.33 +				example 1: connections from whitelisted IP addresses to the service are allowed, while connections from all other IP addresses are rejected;
    1.34 +				example 2: connections from whitelisted IP addresses to the service are allowed, connections from blacklisted IP addresses are dropped (the will not get a any response) and connections from all other IP addresses are rejected (will get a negative response);
    1.35 +			</text>
    1.36 +		</explanation>
    1.37 +		<tag>computer</tag>
    1.38 +		<tag>security</tag>
    1.39 +	</concept>
    1.40 +	<concept>
    1.41 +		<term abbreviation="" completeForm="grey list" language="en"/>
    1.42 +		<term abbreviation="" completeForm="grey-list" language="en"/>
    1.43 +		<term abbreviation="" completeForm="greylist" language="en"/>
    1.44 +		<term abbreviation="" completeForm="greylisting" language="en"/>
    1.45 +		<term abbreviation="" completeForm="gray list" language="en"/>
    1.46 +		<term abbreviation="" completeForm="gray-list" language="en"/>
    1.47 +		<term abbreviation="" completeForm="graylist" language="en"/>
    1.48 +		<term abbreviation="" completeForm="graylisting" language="en"/>
    1.49 +		<explanation language="en">
    1.50 +			<text>
    1.51 +				a method of preventing e-mail spam;
    1.52 +				1) utilizes standard behavior of legitimate e-mail servers that tries to redeliver the message multiple times when a temporary error occurs
    1.53 +				2) expects that spammers are not going to redeliver in that case, because they are focused more on quantitiy than quality (few lost messages are not an issue for them);
    1.54 +				MTA equiped with a greylisting filter will respond with a simulated temporary error to incomming messages from an unknown sender;
    1.55 +				when the sender attempts to deliver the massage for the second time, the message will be accepted (if it is long enough after the first attempt);
    1.56 +				this method is stateful which means that the MTA server needs to maintain a list of senders and their send attempts – this list is called greylist;
    1.57 +				disadvantage of this method is that it causes delays in the e-mail delivery;
    1.58 +				this disadvantage can be partially mitigated using a whitelist: trusted senders (domains or IP addresses) are put on the whitelist and do not have to wait even if they are sending the first message
    1.59 +			</text>
    1.60 +		</explanation>
    1.61 +		<tag>computer</tag>
    1.62 +		<tag>messaging</tag>
    1.63 +	</concept>
    1.64 +	<concept>
    1.65  		<term abbreviation="SQL" completeForm="structured query language" language="en"/>
    1.66  		<term abbreviation="SEQUEL" completeForm="structured english query language" language="en"/>
    1.67  		<explanation language="en">