Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

It's fairly easy, you'll simply need to disable the acceptance of cookies that were set up originally to make things easier for users. This is easy enough, you simply disable their acceptance on your server, or alternatively, set up a "blank" cookie, that errors out any existing cookies, and causes the browser to pop up another password box. Naturally, if you zap the cookie code in your website pages, the cookies are nothing but wasted space on the users drives.

Basically, there are a lot of ways to do this, most of which is pretty basic programming knowledge/website scripting, but it's not something your average MS admin/network guy is going to be able to properly address, because most of those folks barely do the minimum to keep their jobs. Using IE, after most companies, security organizations, governments, etc., have migrated to more secure browsers, just shows how far your firm still has to go simply to catch up to minimally acceptable security standards, so worrying about cookies and logins from internal users is kind of missing the point.

Sorry, but cookies don't mean much when viruses, spyware, adware, keyloggers, and a multitude of other problems are the more relevant threat.