Free logins software for linux

Passwordless remote logins script can be used to:

1: Create 1024 bit passwordless dsa keys.
2: Send key to remote server via scp.
3: Create remote .ssh directory and move key to authorized_keys file.

This will allow you to login to remote server via ssh or run automated rsync backups. You need openssh, bash and expect installed for this to work. Optionally you can create an executeButton with the following format for a one click remote server login.

The format: konsole -e ssh -i /your/path/toyour-key remoteusername"@"remotehost_or_ip

fancylogin is one of the most powerful login programs available for Linux. It can do everything your old login program can do, e.g., handling shadowed passwd files, user-time-terminal/network-verification as done with HP-UX login, etc. The project adds a lot of capabilities for logging logins and support for themes to control the logins look.

History:

I first had the idea of creating a better login for linux, when i was working for IBM in the summer. a really big company had lots of 5250 terminals standing around. OS/400 would allow you (just like fancylogin) to insert an ascii-graphic with colors, etc., so all terminals were showing the companys emblem. this really looked great. so why is it, that one of the best server-systems like linux has such a boring login-screen? even Novell Netware has at least bits of color!

The more i studied popular login-programs, such as Julienne Haughs shadow-login, the more i realized that much more capabilities for security and logging are needed, in order to guarantee a secure system. fancylogin shouldnt only be a a fancy login but also a secure and very functional one. And as everybody who wants to do something on a system must be authenticated by a login, a good login-program is one of the most important keys to a secure and reliable system. fancylogin should be the answer.

The first thing i did was write a litte fancy.o with really weird configuration (the signon.*-files). then i had a look at the sources of the shadow-login-program and included a call to my fancy_prompt-routine. that was all. but as i didnt know anything about that code, i decided to take my fancy.o and write my own login-program around it, because i had a lot of improvements in mind. that was in the christmas-holidays of 1999. after those holiday fancylogin 0.99.5 was out, and the first login program that supported techniques from shadow AND from HP-UX-login (usertty). that was when Andreas Krennmair joined the team. soon we released 0.99.6, and for the first time announced it in c.o.l.a. and on freshmeat.net. on the first day of the release we got 5000 hits, and our school-server had three times the workload it usually had. that was when we put the project on sourceforge.

If i had to give a codename to fancylogin 0.99.7 i would call it "0.99.7 - the great odyssee". first we released some minor patches and fixes in 0.99.6b, but we had great plans for 0.99.7. priority number one was an improved way of configuring everything. then Matthew Wormald wrote an email doing suggestions on fancylogin. one of these were to support ANSI-files, which was the solution of our dilemma. then i worked on support for ANSI-files, but just couldnt get an ANSI-interpreted terminal together with ncurses. after a few months we decided to forget about the ANSIs, because it was too difficult to implement. Andreas Krennmair wrote flted, a program to create signon*- configurations. it should never really be released, because he finally managed to do it. in fancylogin-0.99.7-alpha2 everything was finished already, with fancylogin supporting the signon.defs and two ANSI-files. but i wanted to have everything in one file, so themes could be easily installed, and every theme-related information was in one file. so i decided to put everything into a structure, and wrote fltcreate and the neccessary modifications to fancy.o, and fancylogin-0.99.7 was finished. the first fancylogin a normal human could actually configure and write themes for!

doinkd project is a "daemon" that runs on a machine to keep an eye on current users. If users have been idle for too long, or have been logged on for too long, it will warn them and log them out appropriately. The types of checks that doinkd performs are the following:

maxuser: *NEW* If a declared number of sessions, either by group or userid, are active, that user and subsequent users/sessions are warned and their sessions are terminated.

idle: If a user is idle more than their allotted time, as specified by the doinkd configuration file, he/she will be warned. If no action has taken place during the warn time, the user will then be logged out.

session: If a user is logged on for longer than the allotted time, he/she will be warned and logged out in warntime seconds if the user is still logged on then.

multiple: If too many user sessions are active (ie. many users logged on, or some users logged on many times), doinkd will choose X many sessions for each user to keep, waning the others, and logging those out in sleep seconds (such as 120) if there are still too many logged in then. X is either specified as a number of multiples per user, or is proportional to the threshold of sessions before multiple logouts are in effect.

refuse: If a user matches this setting, doinkd will terminate the users session after about a 5 second warning. The basically "refuse"s access for that user (or tty, or group) to the machine, though there may be some time allowed when doinkd is sleeping between checks.

doinkd is configurable without recompilation for its settings, such as the maximum allowed idle times, session limits, thresholds before session limits and multiple login checks begin, and also the important exemption lists. The configuration file is automatically re-read every sleep seconds (specified in the configuration file). If the
configuration file missing or contains errors when doinkd attempts to update its configuration, it will simply report the errors to its log file and continue normal operation, either with its previous settings (in the event of the file not being there or not being readable) or with all valid settings (in the event of errors in the conf file). doinkd must exit, however, if the configuration file is doesnt exist or is not readable when it first starts, and will also exit at the start if there are errors in the configuration file (since they should be fixed then).

Exemptions can be set for any user, group, host the user is logged in from, or tty for any of the checks that doinkd performs, such as allowing idle timeouts to default to 60 minutes for everyone, but exempting the staff group from these timeouts.

doinkd has the ability to handle the console as special, so that X-Windows environments can have appropriate settings. The special handling includes giving an idle time, session limit, and allowed multiple logins specifically for the user on console. All of these logout checks can also be disabled for the windows owned by the user on console. Idle activity is found by checking the keyboard and mouse if the user is in X-Windows. Special checking is also done to see if the person on console is running xlock (or some terminal locking program--the name is configurable at
compilation time) and logging the user off if the xlock program runs longer than the allowed console idle time. The special xlock check prevents users from running xlock and leaving the terminal for a long period of time, but not getting logged off, since other users may press a key or move the mouse to see if the machine is available, and in doing so makes the logged in user no longer idle. See TODO file for a comment on xlock. doinkd also has the ability to work with some implementations of XDM.

The configuration files path may be specified on the command line, so that one executable can be used on multiple machines with different path structures. Also, doinkd can read in separate files (specified in the config file) to get a list of users to apply a timeout/session/refuse/exempt command to.

Copernicus provides a program for remembering usernames and passwords.

It enables you to store all your various Internet login details in one convenient location. It is easy to use, free, cross-platform, and available in more than ten different languages.

Copernicus is a username and password remembering program that enables you to store all your various internet login details in one convenient location. Rest assured, it is totally free from spyware and adware which tend to haunt this type of program. Apart from its ease of use, other benefits of Copernicus include the fact that it doesnt cost you a cent, is open source, will work on most modern computing platforms such as Linux, Mac OS X and Windows, and is available in more than ten different languages.

Copernicus is extremely easy to use - as you can see from the screenshots listed on this page, all of your sites are listed on the left hand side. If you click on one of those sites - the associated login details (username, password and any other information you require) are displayed on the left. Due to the fact many people have multiple logins for a single site - you can even have several logins associated with the one site and can browse the other ones by clicking on the login drop down box, or clicking the shortcut for the next login (denoted by the > symbol).

Copernicus is well suited to a multi-user computer as each user can have their own copernicus file where they store their logins.

Like all Tank Software programs, Copernicus strives to be highly customisable. You can change the language that Copernicus uses to one of the many included translations (there are over ten, including French, German, Greek, Japanese, Russian and Spanish). If you dont like the Look & Feel (a.k.a the GUI theme), you can choose between the Kunststoff Java Metal theme (default, example at top), your System default theme (Windows, example at bottom) the standard Java theme or even a custom Java Look & Feel.

As stated above, Copernicus is accessible by most computer users supporting many different languages and operating systems.

Multi-Protocol Remote Login provides a middleware allowing SSH, telnet, and local logins from the login: prompt.
MPRL is a middleware application between a *getty program and SSH, telnet, and other such remote-login protocols. It allows a user at a Linux terminal to log into other systems without needing a valid local user-id. It currently supports telnet, ssh, and /bin/login.
It syntax follows the [protocol:]user[@host][:port] fashion.
These are valid logins:
- buanzo - Normal local login: /bin/login gets called.
- buanzo@linux.org.ar - SSH protocol by default: /usr/bin/ssh gets called
- ssh:buanzo@webserver.algo.net

Lachesis IRCRPG Combat Engine project is an IRC bot/RPG engine in C and C++.
Lachesis is an IRCRPG combat engine written in a combination of C and C++. The combat engine is being written for a specific RPG, but most of the project should be useful to IRCRPGs in general.
It includes a native interface to the IRC protocol to allow it to act as an IRC bot, for such uses as dice rolling and acting as a remote-controlled client (RPG NPC perhaps).
Enhancements:
- Auth_TUHCB has new method MatchNick
- Clarified a problem with failed logins shortly after joining a channel
- Util_Getline no longer exists
- Data format has changed
- data/users/master has become data/master
- Fixed irc.h so that lowlevel IRC interface neednt be in C
- Minor changes to prepare for CVS import
- Moved the sample data to example/data/
- Added a script to create and delete lachesis users in example/scripts/
- Added new utils functions

Fingerfox works like a workaround to make MS Fingerprint Reader fill the forms of a web page shown in Firefox. To avoid security problems (with login and password storage in particular), it relies with DigitalPersona to do it and just act as a popup window which repeats the login forms (including the buttons).

Then it remembers on which page and which form it has been used and popup automatically the next time you need to log in so that you can use firefox with your fingerprint almost as easily as IE.
It is now compatible with HTACCESS type logins.

Lynx is a fully-featured WWW client for users running cursor-addressable, character-cell display devices (e.g., vt100 terminals, terminal emulators running on PCs or Macs, or any other character-cell display).
Lynx will display HTML documents containing links to files on the local system, as well as files on remote systems running HTTP, HTTPS, gopher, FTP, WAIS, NNTP, finger, or cso/ph/qi servers, and services accessible via logins to telnet, tn3270, or rlogin accounts.
Enhancements:
- Several unrelated fixes and improvements were made for configuring, packaging, FTP, SSL, etc.