From 96846ef9002588425ec86dd2f474ecdf576acbb6 Mon Sep 17 00:00:00 2001 From: LoRd_MuldeR Date: Mon, 29 Dec 2014 01:34:49 +0100 Subject: [PATCH] Manual: Added some topics the the FAQ section. --- doc/Manual.html | 4 ++++ doc/Manual.md | 7 +++++++ src/Config.h | 2 +- 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/Manual.html b/doc/Manual.html index 07de0916..14e7eaad 100644 --- a/doc/Manual.html +++ b/doc/Manual.html @@ -81,6 +81,7 @@
  • 8.3 Q: How can I donate to the authors of LameXP?
  • 8.4 Q: Why is this software called LameXP?
  • 8.5 Q: Why are the LameXP binaries not digitally signed?
    • +
  • 8.6 Q: Why does LameXP connect to (random) web-servers?
    • @@ -498,6 +499,9 @@ EBBqQT1s8/oi0RsAniNAOQRb8roflIOXVmeW3uB50RVtAJwLS5O19VD1W0HxjNZ6 sE7XdEZn+w== =WDwE -----END PGP PUBLIC KEY BLOCK----- +

    8.6 Q: Why does LameXP connect to (random) web-servers?

    +

    A: LameXP does not connect to any web-server, except for the "automatic updates" feature. Of course, in order to check for new updates, LameXP unavoidably has to communicate with our update servers. However, in no event LameXP will search for updates without your consent. Also, LameXP will not send any personal information to the update server. Instead of uploading your information, e.g. your current program version, to the web-server, LameXP will download the update information from the update server and compare it to your installed version locally. Furthermore, all information and program files downloaded from the update servers are protected by PGP (GnuPG) signatures, in order to assure the authenticity and integrity of these files. Files with missing/invalid signature are going to be rejected, so (spoofing) attacks are prevented.

    +

    Note: Before LameXP actually tries to download information from our update servers, it will check your internet connection first. Only checking whether the update server is reachable does not suffice here. In case that the update server does not respond, this could mean that our servers are currently experiencing problems, but it could also mean that your Internet connections is failing. In order to distinguish these cases, LameXP will validate the Internet connection prior to connecting to the update server. For this purpose, LameXP contains a rather long list of "known" hosts, taken mostly from Alexa's Top 500 list. In order to validate the Internet connection, LameXP will pick a random host from the list and check whether that host can be reached. This process will be repeated, until a certain minimum number of "known" hosts have been reached successfully.

     
     
    EOF

    diff --git a/doc/Manual.md b/doc/Manual.md index 8c30d4e9..a06c393f 100644 --- a/doc/Manual.md +++ b/doc/Manual.md @@ -699,6 +699,13 @@ If you want to verify the LameXP signatures yourself, then you may do so by usin -----END PGP PUBLIC KEY BLOCK----- +## Q: Why does LameXP connect to (random) web-servers? ## + +**A:** LameXP does **not** connect to any web-server, except for the "automatic updates" feature. Of course, in order to check for new updates, LameXP *unavoidably* has to communicate with our update servers. However, in **no** event LameXP will search for updates *without* your consent. Also, LameXP will **not** send any personal information to the update server. Instead of *uploading* your information, e.g. your current program version, to the web-server, LameXP will *download* the update information from the update server and compare it to your installed version locally. Furthermore, all information and program files downloaded from the update servers are protected by PGP (GnuPG) signatures, in order to assure the authenticity and integrity of these files. Files with missing/invalid signature are going to be *rejected*, so (spoofing) attacks are prevented. + +*Note:* Before LameXP actually tries to download information from our update servers, it will check your internet connection first. Only checking whether the update server is reachable does **not** suffice here. In case that the update server does **not** respond, this could mean that our servers are currently experiencing problems, but it could also mean that your Internet connections is failing. In order to distinguish these cases, LameXP will validate the Internet connection prior to connecting to the update server. For this purpose, LameXP contains a rather long list of "known" hosts, taken mostly from [Alexa's Top 500](http://www.alexa.com/topsites) list. In order to validate the Internet connection, LameXP will pick a *random* host from the list and check whether that host can be reached. This process will be repeated, until a certain minimum number of "known" hosts have been reached successfully. + +     diff --git a/src/Config.h b/src/Config.h index dd44ab16..7e176f9e 100644 --- a/src/Config.h +++ b/src/Config.h @@ -35,7 +35,7 @@ #define VER_LAMEXP_MINOR_LO 1 #define VER_LAMEXP_TYPE Beta #define VER_LAMEXP_PATCH 12 -#define VER_LAMEXP_BUILD 1658 +#define VER_LAMEXP_BUILD 1660 #define VER_LAMEXP_CONFG 1558 ///////////////////////////////////////////////////////////////////////////////