Free cookie files software for linux

allcookies is an extension which dumps ALL cookies (including session cookies) to Firefox standard cookies.txt file.

The mandatory companion tool for downloading sites with WGET
A very minimum extension : no psychedelic design. Just the needed feature.

Why you need it : Many web sites are protected by either
- authentification forms
- vicious access rules like "you must first see some introductory or advertisement pages"

Such sites cant be downloaded with the well known WGET tool

AllCookies is the answer to this kind of restrictions.

How it works

Web sites generally use temporary "session cookies" to manage access rules. Such cookies are not saved to the firefox "cookies.txt" file, and are destroyed once your session closes.

AllCookies will turn those cookies to permanent cookies and force saving in cookies.txt

A typicall scenario to download a web site with WGET becomes:
- using Firefox, connect to the web sites, go through all the authentification forms or preliminary pages that are required
- execute AllCookies (just a simple item added in Firefox menu ) to update cookies.txt file
- launch wget : wget --load-cookies=z:cookies.txt http://foo.com

Kernelcookies project consists of fortune cookies from the Linux Kernel.
Kernelcookies is a datafile for fortune that contains some of the funnier or more obscure kernel messages.
One of the most famous messages ("lp1 on fire") was part of the linuxcookies data file (and got me started on this compilation).
NOTE: Some of the cookies may contain offensive language. As I dont really want to decide on what someone might find offensive or not and create two seperate files, I only put this warning here. If you dont want offensive fortunes, youll have to weed this file out yourself.
Enhancements:
- 25 new cookies from Linux 2.6.19 were added.

Auth MemCookie is an Apache v2 authentification and authorization modules are based on "cookie" authentification mecanism.

The module dont make authentification by it self, but verify if authentification "the cookie" are valid for each url protected by the module. The module validate also if the "authentificated user" have authorisation to acces url.

Authentification are made externaly by an authentification form page and all authentification information nessary to the module a stored in memcached indentified by the cookie value "authentification session id" by this login page.

How it Works

Phase 1 : The login Form

Authentification are made by a login formular page.
This login page must authenticate the user with any authenticate source (ldap, /etc/password, file, database....) accessible to langage of the page (php, perl, java... an ldap login page sample in php are in samples directory).

Then must set cookie that contain only a key the "authentification unique id" of the "authentification session".

The login page must store authorisation and user information of the authenticated user in memcached identified by the cookie key "authentification unique id".

The login page can be developted in any langage you want, but must be capable to use memcached (they must have memcache client api for us)

Phase 2 : The Apache v2 Module

After the user are logged, the apache 2 module check on each protected page by apache ACL the presence of the "cookie".

if the "cookie" exist, try to get session in memcached with the "cookie" value if not found return "HTTP_UNAUTHORIZED" page.

if session exist in memcached verify if acl match user session information if not match return "HTTP_FORBIDDEN" page.

Enhancements

• Some bugs are fixed
• A menu is added

Requirements:

• Python
• Pygame

X-Files is a graphical file management program for Unix/X-Window environment. It was inspired by the Amiga program DirWork.

This application differs slightly from the main stream file managers in that it has always only one window. On top (or bottom) of the window you have ActionbuttonsTM -area. Other main areas are the two directory listings for file related actions. You can use quick pop-up menu for basic operations. File extensions can be configured to launch any program you desire for that file.
The appearance and functionality can be fully configured according to your taste using the built-in editors.

Tested on: Intel Linux, DEC Alpha, SGI, HP-UX, Solaris
(Should work on any Unix-machine running Tcl/Tk.)

QArchive.org web files checker is an extension which allows people to check web files for any malware.

The add-on allowing people to check web files for any malware (viruses, trojans, worms, adware, spyware and other unwanted things) inclusions. Install this plug-in to your browser, reload it. Then click the web file link by right mouse button and choose a "Check files with QArchive.org".

Then follow web site instructions. The usual way: your file will be enqueued. Refresh the report page to get completete antivirus report. That will show you all web files part checking and a summary as well. If you are a web master you can you the useful feature.

Taking the code of received report and placed it on your web site you can inform people about a concrete file safety. The web forums code version exists as well.

mod_auth_cookie_dbm is a session authentication/expiration using (cryptographically strong) cookies. Cookie-to-username mapping with DBM database.

It was devised as a better replacement for the "Basic" authentication components that ship with Apache.

Classic "Basic" authentication has some downsides:

- Username and password are shipped across the net with every request.
- There is no concept of a "session" (nor encores, such as timeouts and automatic logout)

This module

1. checks requests for a cookie, named in the CookieDBMAuthCookieName configuration directive.

2. If found, the cookie value is looked up in a DBM database, named in the CookieDBMAuthFile directive.
If the lookup fails, a redirect is made to a page specified in the CookieDBMAuthFailureURL directive.

3. The DBM entry is expected to contain a username and optionally an expiry time. Fields are colon-separated, the expiry time is a spelled-out integer (the field gets passed to strtol()) representing the time_t
If valid, the username is taped onto the request, thus "emulating" Basic authentication.
If expired, redirect to the CookieDBMAuthFailureURL.

The CookieDBMAuthFailureURL typically points at a "login page" CGI script. This program, after checking the users credentials, should make up a cookie value (preferably a long, cryptographically strong random string), enter it in the dbm file, and pass it to the browser. It might also update an AuthUserFile or AuthDBMUserFile database on the fly.

Acknowledgements:

This module was written from scratch, with some inspiration from the mod_auth_cookie_mysql and mod_auth_cookie_pgsql2 modules.

mod_auth_cookie_mysql2 is a rewrite of the mod_auth_cookie_mysql module for apache 1.3. Some features were added, some were forgotten.
The module is available for apache 1.3 (mod_auth_cookie_mysql1) and apache 2 (mod_auth_cookie_mysql2). It is tested with mysql 3.x/4.x and and 5.0.x.
The current version of of this module is version 0.7.
If you want to receive a message when a new version is released, please leave your e-mail address in the announcements field at the left top of this site. This will register you to a moderated mailing list. Your e-mail address, will be kept private, it isnt visible to other users and it will not be distributed.
Basic auth is a standard authentication method in the internet. Two big disadvantages are, that on every request the username and password are transmitted to the webserver and there is no possibility to log out without closing the webbrowser.
With this module you can authorize your users with cookies. An external script sets the cookie and this module checks it against a MySQL database. The username/password combination is only one time transferred to the webserver when the external authenticator script (which sets the cookie) checks the user data. The generated cookie consists only of random session data.
So you can, for example, authenticate the user and set the cookie in a ssl connection and then use the cookie in a non-ssl environment and nobody can spy the username/password. Since the cookie is only random session data nobody can "hack" the system by manipulating the cookie values. Additionally you can add checks for session expiry and the correct remote ip on the server side.
Main features:
- Fake Basic Auth with cookies
- Cookie only consists of random session data, no username or password
- Can check expiry information stored in database against cookie
- Can check if the remote IP is equal to the IP stored in database
Enhancements:
- bug fix: return-code of function check_valid_cookies not initialized - thanks to Valerii Valeev