100SILEX, de 0 100 s: Hopefully,
1522 5 Simple steps to secure TT-RSS reader
secure tt-rss, tt-rss security 5 Simple steps to secure TT-RSS reader July 27, 2015 by Anand Leave a Comment secure-tt-rss-ft Share: share htpcBeginner We recently presented Tiny Tiny RSS to you as a great alternative to Google reader, which is one more way you can extend the functionality of your home server or your hosting space. Hopefully, you already exported your data from Google Reader. In this post, we will show you how to secure TT-RSS reader to prevent unauthorized access. Tiny Tiny RSS is an open source web-based news feed (RSS/Atom) reader and aggregator, designed to allow you to read news from any location, while feeling as close to a real desktop application as possible. As we previously explained, it makes an ideal candidate to replace Google Reader. While there are services like Feedly and Newsblur grabbing the crowd Google Reader, which some of you may prefer, there are a group of people who would like to run a RSS reader on their own server and keep things private. Assuming that you have already installed Tiny Tiny RSS on your alternative to Google reader or hosting space, we will now show you how to secure TT-RSS reader. Secure TT-RSS Reader One of the main reasons to move to an RSS aggregator like TT-RSS is maintaining your privacy. So if you do not secure TT-RSS reader well you are not only making your data available public but also making your system vulnerable to potential attacks. Choosing a strong username and password while setting your TT-RSS is the first basic thing that you can do to secure TT-RSS reader. Listed below are few more ways you can increase TT-RSS reader’s security. 1. Rename TT-RSS Folder One of the first lines of defense is to not use tt-rss in your URL to access your TT-RSS reader. To do this on your hosting account, use a folder name other than tt-rss while installing TT-RSS. On your Linux home server, edit /etc/tt-rss/apache.conf and change the first /tt-rss to something else. An example is shown below. TT-RSS Rename URL TT-RSS Rename URL After making the change, restart your TT-RSS and Apache to apply the changes: sudo service tt-rss restart sudo serivce apache2 reload Your TT-RSS reader is now available through the new URL (example: http://mydomain.com/myreader) only. Amazon Kindle Fire HDX 2. Enable SSL Accessing TT-RSS through http sends all information as unencrypted data. This could mean less privacy due to potential sniffing. The solution is to encrypt the data during transfer, which makes sniffing by hackers harder. To enable and enforce HTTPS access on Linux servers with Apache, install the following run-time libraries: sudo apt-get install libssl0.9.8 libpam0g openssl Restart your Apache server as shown above. You should now be able to access your TT-RSS reader with HTTPS. Note that you may have to have a SSL certificate generated. Refer to Apache documentation if you want to generate your own certificate. By default, the system will install self-signed certificates for you. These certificates are likely to raise warnings when you point your browser to the site. 3. Disable Single User Mode By default the single user mode is already disabled (in /etc/tt-rss/config.php). Enabling single user mode will also disable TT-RSS login system. Therefore, keep the single user mode disabled. Disable Single User Mode Disable Single User Mode A better way to make it a single user system is by limiting the number of registrations to 1 as described below. For whatever reason, you still want to enable single user mode, make sure you implement Apache Authentication method described below. 4. Self Registrations Self registrations allow a visitor to register themselves, which could reduce TT-RSS security. If your TT-RSS will be for personal use only, then you may want to disable user registration by setting “ENABLE_REGISTRATION” to “false”. TT-RSS Self Registrations TT-RSS Self Registrations To further secure TT-RSS Reader, uou may also want to change “REG_MAX_USERS” to “1” to make your account the only account on TT-RSS. asus n66uASUS RT-N66U Dual-Band Wireless-N900 Gigabit Router asus n66u reviewsFind out why it is rated the best wireless router in its class. 5. Apache Authentication Last but not the least, enable Authentication. This is even more important if you have enabled “Single User Mode” describe above. Every time you access TT-RSS, you will be asked for a username and password as shown in the picture below: Secure TT-RSS Reader On your hosting account this equivalent to password protecting a directory, in this case the TT-RSS directory. To do this on your Ubuntu server, you will have to create a .htpasswd file. More information is available in Apache documentation. But the easiest way to achieve this is to use one of the htpasswd generators available online. After you enter the username and password two code blocks will be generated. Copy the contents of the .htpasswd code block and save it to /etc/apache2/.htpasswd_ttrss. Next, copy the contents of the .htaccess code block and add it to /etc/tt-rss/apache.conf as shown below: TT-RSS Apache Authentication TT-RSS Apache Authentication Save and exit. Restart both TT-RSS and Apache previous shown above. You should be prompted for a password every time you try to access TT-RSS. Some may think that this double authentication method is an extra inconvenience. But I would rather be safe than sorry. Go ahead, secure Tiny Tiny RSS Reader and enjoy reading articles on your private secure RSS Reader.

687 50 Beautiful and Fresh Free Fonts
As you will already know, there are thousands upon thousands of free fonts available, so choosing that perfect font can be very, very difficult. Its tedious business constantly scouring through countless font directories and foundries to hopefully find what you are looking for. Hopefully, with this post, we can make your search that little bit easier by rounding up 50 of our favorite fonts that have been released in recent months. So, whether you design web pages, t-shirts, posters or just seeking some typographical inspiration, we have no doubt that you will the perfect font for your perfect project in this round-up. Please note, licenses to have a tendency to change so please double check before usage.

364 What every programmer should know about memory, Part 1 [LWN.net]
Editor's introduction: Ulrich Drepper recently approached us asking if we would be interested in publishing a lengthy document he had written on how memory and software interact. We did not have to look at the text for long to realize that it would be of interest to many LWN readers. Memory usage is often the determining factor in how software performs, but good information on how to avoid memory bottlenecks is hard to find. This series of articles should change that situation. The original document prints out at over 100 pages. We will be splitting it into about seven segments, each run 1-2 weeks after its predecessor. Once the entire series is out, Ulrich will be releasing the full text. Reformatting the text from the original LaTeX has been a bit of a challenge, but the results, hopefully, will be good. For ease of online reading, Ulrich's footnotes have been placed {inline in the text}. Hyperlinked cross-references (and [bibliography references]) will not be possible until the full series is published. Many thanks to Ulrich for allowing LWN to publish this material; we hope that it will lead to more memory-efficient software across our systems in the near future.

101 - 201