Free facebook login page user software for linux

Address Book Continued provides a multi-user AJAX address book Web application.

It also makes use of AJAX, which means that page reloads only happen on login/logout; the rest of the operations is handled asynchronously in the background. Its well usable, even over slow connections.

You can even install ABC on your desktop PC and configure it so that it doesnt require login for connections coming from the local computer.

NewsCloud Facebook application allows Facebook members to read top stories and breaking news and share them with their friends from within Facebook.
The NewsCloud Facebook application also allows you to watch Daily Show and Colbert Report clips inside Facebook and share them with other Facebook members. Facebook is a social network with a new API for applications. NewsCloud is an open source collaborative social news network.
As the documentation to Facebooks API is still incomplete, the source code to the NewsCloud Facebook application may be instructive to other Facebook developers.
Enhancements:
- Added support for multi-friend selector with thumbnail images
- Added SQL table structures

WWW::Facebook::API::REST::Client::Login is a Perl module to ask for user login info.

SYNOPSIS

use WWW::Facebook::API::REST::Client::Login;

This uses the WWW::Mechanize object to login a user to the Facebook. Useful for quick testing, by replacing WWW::Facebook::API::REST::Client::Auth in Client.pm with this module since this module subclasses that one.

SUBROUTINES/METHODS

base

The WWW::Facebook::API::REST::Client::Base object to use to make calls to the REST server

login_uri

The login uri for having the user login. If you want, there are internal methods available (using WWW::Mechanize) to login the user automatically so they dont have to open a browser window to do so.

login

Given a token, logs in a user using _login_form.

INTERNAL METHODS AND FUNCTIONS

_login_form

Generates the actual form submission for the login process. Ask for the user name and password of a person from STDIN. Their username and password is not masked presently, and it is not stored (the latter of which is a BIG no-no).

DCE::Login is a Perl extension for interfacing to the DCE login API.

SYNOPSIS

use DCE::Login;
my($l, $status) = DCE::Login->get_current_context;
my $pwent = $l->get_pwent;

Perl extension for interfacing to the DCE login API.

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.

Apache2::AuthCookieDBI is an AuthCookie module backed by a DBI database.

SYNOPSIS

# In httpd.conf or .htaccess

PerlModule Apache2::AuthCookieDBI
PerlSetVar WhatEverPath /
PerlSetVar WhatEverLoginScript /login.pl

# Optional, to share tickets between servers.
PerlSetVar WhatEverDomain .domain.com

# These must be set
PerlSetVar WhatEverDBI_DSN "DBI:mysql:database=test"
PerlSetVar WhatEverDBI_SecretKey "489e5eaad8b3208f9ad8792ef4afca73598ae666b0206a9c92ac877e73ce835c"

# These are optional, the module sets sensible defaults.
PerlSetVar WhatEverDBI_User "nobody"
PerlSetVar WhatEverDBI_Password "password"
PerlSetVar WhatEverDBI_UsersTable "users"
PerlSetVar WhatEverDBI_UserField "user"
PerlSetVar WhatEverDBI_PasswordField "password"
PerlSetVar WhatEverDBI_CryptType "none"
PerlSetVar WhatEverDBI_GroupsTable "groups"
PerlSetVar WhatEverDBI_GroupField "grp"
PerlSetVar WhatEverDBI_GroupUserField "user"
PerlSetVar WhatEverDBI_EncryptionType "none"
PerlSetVar WhatEverDBI_SessionLifetime 00-24-00-00

# Protected by AuthCookieDBI.
< Directory /www/domain.com/authcookiedbi >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
PerlAuthenHandler Apache2::AuthCookieDBI->authenticate
PerlAuthzHandler Apache2::AuthCookieDBI->authorize
require valid-user
# or you can require users:
require user jacob
# You can optionally require groups.
require group system
< /Directory >

# Login location.
< Files LOGIN >
AuthType Apache2::AuthCookieDBI
AuthName WhatEver
SetHandler perl-script
PerlHandler Apache2::AuthCookieDBI->login
< /Files >

This module is an authentication handler that uses the basic mechanism provided by Apache2::AuthCookie with a DBI database for ticket-based protection. It is based on two tokens being provided, a username and password, which can be any strings (there are no illegal characters for either). The username is used to set the remote user as if Basic Authentication was used.

On an attempt to access a protected location without a valid cookie being provided, the module prints an HTML login form (produced by a CGI or any other handler; this can be a static file if you want to always send people to the same entry page when they log in). This login form has fields for username and password. On submitting it, the username and password are looked up in the DBI database. The supplied password is checked against the password in the database; the password in the database can be plaintext, or a crypt() or md5_hex() checksum of the password. If this succeeds, the user is issued a ticket. This ticket contains the username, an issue time, an expire time, and an MD5 checksum of those and a secret key for the server. It can optionally be encrypted before returning it to the client in the cookie; encryption is only useful for preventing the client from seeing the expire time. If you wish to protect passwords in transport, use an SSL-encrypted connection. The ticket is given in a cookie that the browser stores.

After a login the user is redirected to the location they originally wished to view (or to a fixed page if the login "script" was really a static file).
On this access and any subsequent attempt to access a protected document, the browser returns the ticket to the server. The server unencrypts it if encrypted tickets are enabled, then extracts the username, issue time, expire time and checksum. A new checksum is calculated of the username, issue time, expire time and the secret key again; if it agrees with the checksum that the client supplied, we know that the data has not been tampered with. We next check that the expire time has not passed. If not, the ticket is still good, so we set the username.

Authorization checks then check that any "require valid-user" or "require user jacob" settings are passed. Finally, if a "require group foo" directive was given, the module will look up the username in a groups database and check that the user is a member of one of the groups listed. If all these checks pass, the document requested is displayed.
If a ticket has expired or is otherwise invalid it is cleared in the browser and the login form is shown again.

PowerPhlogger is a counter hosting and website statistics tool. It lets you offer counter service to others from your site. PowerPhlogger is built on PHP and requires a the MySQL database server.
Your members dont need any PHP-support on their webserver. They just pass the required data through JavaScript to PPhlogger that is hosted on your server.
Currently development of Phlogger3, the future version of PowerPhlogger, is still going on and its source has not yet been opened to public.
This future version will be based on the Sourdough framework and will support various different database systems as backend. It will be a whole rewrite of the existing PowerPhlogger code.
Main features:
Logging:
- user sign-up page that allows users to create accounts
- logs host/ip (proxy & real IP !!), referer, agent, time&date, resolution&color, online-time, pageimpressions
- traceroutes by above.net
- stores IP-adress+cookie to avoid multiple hits by the same user (you can set a timeout)
- multiple page count - include PPhlogger on ALL your pages throughout your whole site
- mail-notice - PPhlogger sends you an email every xx hits
- phlogview - view all data and get a mySQL-dump for backup purposes (incl. logs-by-date search)
- optional: download-count
- Top X referers, Top keywords (single-word or full-string mode)
- Top X domains, Top territories
- Top resolution, Top color
- browser/OS stats
- Calendar - shows your daily/monthly unique hits or pageimpressions
- Visitors per day / per hour graph
- enable/disable your own hits (set a cookie)
- show/hide referers in logs
- (re)set your page hits
- delete entries in your logfile
- demo-mode to make stats avail. to public
- generate a pic to make hits visible on your page (requires GD-library!) - user may choose his own TTF-font, bg/fg-color, font-size >>> unlimited styles!!
- CSS-editor: user may create his own StyleSheet or choose a default style (phloggstyle / phpeestyle / sahara / cartesia / lila / metal)
- timezone support - user may choose his own GMT-time
- multi-language support with localization files
- average online-time
- supports unlimited alternate URLs
- visitor-path - shows the path were the visitor browsed through your site
- Admin page includes:
- set up new useraccounts and notifies the new user (incl. attachment)
- delete useraccounts, clean-up unconfirmed or expired useraccounts , edit useraccounts
- shows all user-configurations
- mailing-list feature
- plug-ins: FTP-diskspace, multiple file upload
- shows your system status (checks for ports on your server)
- show last X customers that entered Phlogview
- CSS-editor