Free dont tread on me flag software for linux

DONT Let It Burn! (1-click Timer) script is just a very basic, 1-click alarm clock. You set the number of minutes and at that time a sound (which you need to set) will be played. No application is started, the sound is played through the aplay command, so its independent from the player you have installed.

Why?

I know there are tons of much better alarm clocks out there. In fact, this is not supposed to be an alarm clock. Its just a sort of kitchen timer, for computer addicted.

My problem was that i was burning all my food (kinda following, too literally, what Usher says in his song "Let it burn!").

After throwing something in the oven or putting on the cookers i use to go back working on the PC and every time i forget about the food. I cant be bother to set a "full alarm clock", need something REALLY fast that reminds me about the food just some minutes later (and if possible i prefer that such reminder is not the horn of the firemen coming to extinguish the fire i caused)

Installation:

Place dont_let_it_burn.desktop in /home/YOUR_USERNAME/.kde/share/apps/konqueror/servicemenus

Place dont_let_it_burn.sh in /home/YOUR_USERNAME/bin

Place dont_let_it_burn.au in /home/YOUR_USERNAME/bin

IMPORTANT: you need to point to a valid audio file, supported bu the apply command (wav or au for example). I have included a small sample file, dont_let_it_burn.au, if you place it in the bin directory then you dont need to do anything else. If you want another file just modify dont_let_it_burn.sh setting a valid path in the variable FULL_PATH_TO_AUDIO_FILE

stephanie is a program for hardening OpenBSD for multiuser environments.

Mmmmm, OpenBSD. Functional, secure, free. With an emphasis on security and integrated cryptography, it carries an excellent reputation for plain old "you-just-cant-hack-this-ness". Not perfect, but nothing is, at least theyre not wearing suits and lying to you.

There are a few roles where i believe OpenBSD fits perfectly. One of these is in multiuser environments, where you have large numbers of possibly malicious users with local access. Here the OpenBSD teams commitment to auditing and fixing code provides a level trust in the environment which is hard to find elsewhere. Also, their efforts to provide integrated cryptography means setting up secure access is easy. So, lets take advantage of the freely available source and tailor it to our specific needs.

Details:

In Phrack 54, route|Mike Schiffman wrote a series of patches for OpenBSD 2.4 for Trusted Path Execution (TPE). Stephanie brings a modified version of these up to speed for OpenBSD 2.8 - 3.0, along with some additional features. A trusted path is one where the parent directory is owned by root and is neither group or other writeable. The TPE works off an internal list of trusted user ids. If a given user tries to execute a file not in a trusted path, and their user id is not in the kernels trusted list, they are denied execution privileges. In real terms, this means they cant download, compile and run krad-sploit.c.

In addition to the TPE, a series of privacy patches came along too. Originally supplied as patches for the individual utilities, these are now implemented through kvm(3), and honour trusted users (ie, trusted users are allowed to see all system information). As a practical example, this means that untrusted users will only be able to see information about processes they own, and the stat tools (netstat, iostat, vmstat, etc) will generally be broken for them. It has been pointed out that by going through trying to kill every possible process id you can find other users processes, but you cant really gain any information on them, so this is not really a great concern.

The original TPE patches had one known way of bypassing the execution restrictions, which was using shell redirection to allow arbitrary interpreted language scripts to be run (perl, sh, etc). This has been fixed up, but could possibly be a big pain in the ass, so please pay attention. When an interpreter is invoked, like most things, it creates a new process group with a job count of one. When a series of commands are connected via the | character on the command line, all the commands belong to the same process group and the job count represents the number of commands eg ps -ax | grep something | awk {print $1} has a job count of three, and the ps, grep and awk processes all belong to the same process group.

The one exception to this is when a user logs in, where we find their shell has its job count set to zero. So how can we use this to prevent shell redirection for a given set of programs? We need to be able to distinguish between ordinary commands and interpreters. At the moment this is done by setting the immutable flag on them. So, in kern_exec(), if we find an untrusted user executing something with the immutable flag set and a job count greater than zero, we flag the process as being potentially dodgy. Then in other system calls we disallow read()ing from fd 0 (stdin) and things like dup2(0, n) if the process has been flagged.

There are two main disadvantages to this. First is the system will need to be brought down to single user mode if the interpreter needs to be patched, and secondly, people will have a hard time suing to an untrusted user. Of course, when a user has shell, they can still type any commands that could otherwise be placed in a shell script, but at the least, this will raise the bar a bit.

Finally, Stephanie brings restricted symbolic links, ala the openwall patches for linux. As time permits, im still working on adding additional features, and will add bits of the openwall stuff i like. The basic goal is to add an extra layer of security without being a monumental pain in the ass to legitimate users, so some things wont be there. I havent added the additional hard link restrictions of the openwall patch, but will do something about this later as time permits.

Installing:

Step by step instructions are presented in the install guide which comes with the source. Read it all first, but its reasonably straight forward. It would be a good idea to read the original article (local copy) if you havent already.

Its distributed under the original two clause BSD license, mess with it all you want, but dont get cranky at me if it breaks something.

You can also read the tpe_adm(8) man page online.

Devel::Constants is a Perl module that translates constants back to named symbols.

SYNOPSIS

# must precede use constant
use Devel::Constants flag_to_names;

use constant A => 1;
use constant B => 2;
use constant C => 4;

my $flag = A | B;
print "Flag is: ", join( and , flag_to_names($flag) ), "n";

Declaring constants is very convenient for writing programs, but as Perl often inlines them, retrieving their symbolic names can be tricky. This worse with lowlevel modules that use constants for bit-twiddling.

Devel::Constants makes this much more manageable.

It silently wraps around the constant module, intercepting all constant declarations. It builds a hash, associating the values to their names, from which you can retrieve their names as necessary.

Note that you must use Devel::Constants before constant, or the magic will not work and you will be very disappointed. This is very important, and if you ignore this warning, the authors will feel free to laugh at you (at least a little.

By default, Devel::Constants only intercept constant declarations within the same package that used the module. Also by default, it stores the constants for a package within a private (read, otherwise inaccessible) variable. You can override both of these.

Passing the package flag to Devel::Constants with a valid package name will make the module intercept all constants subsequently declared within that package. For example, in the main package you might say:

use Devel::Constants package => NetPacket::TCP;
use NetPacket::TCP;

All of the TCP flags declared within NetPacket::TCP are now available.
It is also possible to pass in a hash reference in which to store the constant values and names:

my %constant_map;
use Devel::Constants %constant_map;

use constant NAME => 1;
use constant RANK => 2;
use constant SERIAL => 4;

print join( , values %constant_map), "n";

Call this script from the Autostart folder, and it will update Kopetes away message for each interval (requires Kopete 0.12 or higher). The away messages are by default defined in ~/.kopete-away-msgs. Each line can contain either:
- a comment (starting with a #)
- flags message
The flags define some properties to each away message. Flags are defined only at the start of the line, beginning and ending with a %. The following flags are supported.
[0-9]*[smhd] Determines how long this message should be shown before a new one is chosen. This is the sleep(1) syntax.
a Only show this message when youre away.
c This line is a command, use its output as away message.
i Show the contents of a file, line by line. The message should contain the path to the file. Do not use ~ but use /home/$USER instead. Empty lines in the included file are skipped.
n Use the next message in the file for the next iteration.
o Only show this message when youre online.
x Dont use this message when looking for a random message. This means this line is only accessible when the former line contains the n flag.
- Show the message less than normal times
-- Show the message even more less
--- Show the message sometimes
To determine your online status, you need to have the Web Presence plugin enabled. By default, it reads the file ~/.webstatus.xml. Adapt the variable below if you store the file somewhere else. The script wont do anything when youre offline or partially away (that is, some protocols are Away, some protocols are Online).
Because the web status plugin is used, the process of retrieving the current webstatus is not really reliable. It may happen that you turn back to online when you set the status on Away in a short time. If this doesnt happen in about 10 seconds after the status change, you may consider the status change as successful.
Example ~/.kopete-away-msgs file:
========================================================================
# Sometimes, show uptime for one minute
%1mc--% uptime
# Fortune rocks, but dont pick too long messages (the length of away
# messages is limited.
%2mc% fortune -s -n 120
# just show Hello world for the default interval
Hello world
# Show a away message for 60 seconds.
%a60% Im away now.
# Ask people to say something when youre online
%o% Please message me!
# Show all contents of the Linux README line by line. Show each line for
# 3 seconds.
%3i% /usr/src/linux/README
# Tell a little story when Im away. These lines must emerge in the
# right order, so mind the n and x flags! The x flags make sure we dont
# start in the middle of the story. And, show each line for about 5
# seconds.
%na5% Goodbye, all you people,
%nax5% Theres nothing you can say
%nax5% To make me change my mind.
%ax5% Goodbye.
==================================================================
Enhancements:
- Ability to query the online/away status directly from Kopete (DCOP). This requires a patched Kopete, see the description for more details on how to proceed.
- Fortune mode: Pick a random line from a given text file.
- First check the online/away status to prevent unnecessary command calls.
- Various bugfixes

Nelit2 Engine project is a game engine.
Nelit2 Engine is a game engine that uses a Model-View-Controller concept. All View-s classes was developed by me, and you can dont worrie about this.
Model-s classes also was developed by me, but you can modify it for your game or write new class and use Model class how abstract.
The engine uses some popular libraries such OpenGL and SDL.
It works on Unix systems and on Windows.
Enhancements:
- Decoding png, bmp, jpg texture-file.
- 3D mesh.
- Cubemap texturing.

By using the library, you can continue using the good old $_SESSION variable, while adding the "remember me" funcitionality to your web application.
Setup:
In order to use CBL RememberMe, runtime configuration variable session.cookie_lifetime should be set in php.ini. Below example sets the lifetime to one week. The lifetime can alternatively be set at runtime by calling session_set_cookie_params.
session.cookie_lifetime = 604800 # in php.ini, set expiration to 7 days
Usage:
Construct the RememberMe object with two parameters; name of the cookie to be used for handling state, and, a boolean flag indicating whether or not the "remember me" functionality should be turned on by default.
To turn on / to turn off the "remember me" functionality, call setRemember function.
When clearing session information (i.e. resetting the $_SESSION object), a special variable $_SESSION[__cbl_rememberme] should be preserved. For this purpose, you can use the clear function.
/* construct the rememberme object */
$gRememberMe = new CBL_RememberMe(rememberme, true);
/* dont remember me */
$gRememberMe->setRemember(false);
/* remember me */
$gRememberMe->setRemember(true);
/* clear session info (replacement for $_SESSION = array()) */
$gRememberMe->clear();
Enhancements:
- The remember function now refers to the $this->default_remember variable when a new user connects.

EPoX wmsensormon is a hack based on the original wmsensormon package, version 1.1.3.
My modified version works out of the box on an 2.6.6 Linux kernel using the w83627hf and i2c-isa modules for hardware sensor monitoring, for an EPoX 8RDA3I motherboard.
Take it or leave it, dont call me for support.
Usage details
Compile by issuing make under the wmsensormon directory. You may need to add some -I and -L flags to the Makefile for your particular setup.
For me it works best when run like this:
wmsensormon -s1 -lf 2850 -lt 50 -ls 24
You can, of course, adjust the limits as you see fit, but only use integer values. Run wmsensormon without parameters to get help. The -lf is the lower CPU fan limit, -lt is the upper CPU and MOB temperature limit, -ls is the upper SYS temperature limit.
I dont use any of the additional features (logging, safety command, temperature switching) so they are untested. SMP support has been mangled and disabled so it most likely wont work in a multi-processor environment.
Options : -h, --help this help screen
-v, --version print version information
-f show temperatures in Fahrenheit
-s default SMP mode (mode #1)
-s1 SMP mode #1 (CPU 1, CPU 2, sys, fan)
-s2 SMP mode #2 (CPU 1, CPU 2, fan 1, fan 2)
-w switch CPU and SYS temperature readings
-r refresh time (in microseconds, default 100000)
-l enable logging with default time, (default 30000)
-ln enable logging with specified time, (1000 = 1 min)
-lt limit CPU temperature, default: system value (i.e. 60)
input values in Celsius
-ls limit SYS temperature, default: system value (i.e. 60)
input values in Celsius
-lf limit fan speed, default: system value (i.e. 3000)
-lv limit CPU core volts, default is system value
either: max voltage first, min voltage second (i.e. 180 170)
or: percent difference first, value second (i.e. % 5 175)
Example command line:
limit temp, fan, volt: wmsensormon -lt 40 -ls 30 -lf 5000 -lv 183 167 -f
using percent and SMP: wmsensormon -lt 40 -ls 30 -lf 5000 -lv % 5 175 -s -f
You must specify at least one command line argument, do to the fact that not everyone has the same CPU, voltage, or fan setup.
Enhancements:
- Hacked by xlife@zuavra.net to work on my new EPoX 8RDA3I.
- Displays CPU, MOB, SYS and FAN and reacts to lf, lt and ls limits.