Free youtube script for sale software for linux

Comment Script is a script that allows comments to be left on any existing PHP or HTML page. By default, Comment Script shows name, e-mail, homepage, title, and comment fields, though any can be disabled.
The "comment" field is mandatory and must be filled out before the form can be submitted. In order to prevent the script from being abused by automatic spam bots, you can enable the CAPTCHA feature.
The script then asks your visitors to enter a text they see in the image below the comment form into an input box. It also features an admin area where comments can be edited and deleted and the front-end language set.
Main features:
- Visitors can enter a name, e-mail, homepage, comment title and comment text
- Comment script can be included in existing web pages
- To prevent comment spam you can enable the Captcha feature
- Admin area for editing and deleting comments
- Completely template driven
- Installation routine
How the script works:
Once you have the script installed on your server you can include it in any existing PHP or HTML page. By default the script shows the form fields "name", "E-mail", "Homepage", "Title", and "Comment". You are free to remove some of the fields and only leave the ones you want.
The field "Comment" is mandatory and the form will not submit until that field has been filled out.
In order to prevent the script from being abused by automatic spam bots, you can enable the Captcha feature. The script then asks your visitors to enter a text they see in the image below the comment form into an input box. The comment will only be submitted if the strings match. Visitors have to ensure that their browser support and accept cookies, otherwise the comment cannot be verified.
The script also features an admin area where comments can be edited and deleted. Also there is a section for settings where you can set the front end language as well as the admin account.

Script for a dual-homed firewall script is intended to setup a masquerading firewall based on the IPTABLES (Net)filter-machanism of Linux 2.3.15+
Syslogging matches fireparse for graphical output (see http://www.fireparse.com)
Normally this script will work out-of-the-box, but you should adapt it to your own needs (At least you should set the correct default interfaces --> see Default-Interfaces section)
Syntax to invoke script: firewall (start|stop|restart|status) EXTIF INTIF
Example: "firewall start ppp0 eth0"
Enhancements:
- Added a few comments

Get YouTube Video is a service menu for KDE.

Usage:
Right-click onto a link to a YouTube video or at the background of the YouTube site showing the video and choose action -> Download YouTube Video -> ...

Install:
cd ~/.kde/share/apps/konqueror/servicemenus/
tar xvzf /path/to/youtube-servicemenu.tar.gz

I made some modifications to the YouTube Service Menu. It didnt work for me, so I looked at the source. I added a differnent method to guess the video_id and I added additional parameters to the query string to download the video.

The query-string trick is:
video_id is a part of the site-url, in which the video is embedded:

video_ids = set(re.findall(www.youtube.com/v/([-A-Za-z0-9_]+), data))

or

m = re.search(video_id=(?P [-A-Za-z0-9_]+), data)

or

m = re.search(v=(?P [-A-Za-z0-9_]+), data)

Then I do:

url = "http://www.youtube.com/watch?v=%s" % video_id

Now url points to a site in which the video will be embedded, so I can apply following regular expression to its contens:

m = re.search(watch_fullscreen?(?P .*?)&fs=1&title=" + "(?P

Tourney Team Stats (tts) is a Python script that creates stats for Quake 2 Team Play.

It can only work with the ngLog logstyle, so the Tourney Quake 2 mod is the only one supported.

Youtube Downloader GUI project is a GUI for the famous python script youtube-dl. It is made in Kommander, so you need it. The project is packed in rpm with icon, desktop file.

openSUSE repo:

http://software.opensuse.org/download/home:/pnemec/SUSE_Linux_10.1/
http://software.opensuse.org/download/home:/pnemec/openSUSE_10.2/

It should work on other distribution too.

IPTables Firewall Script contains two example firewall scripts "rc.firewall.iptables. Ive tried here to give some brief documentation for the IPTables firewall scripts contained in this directory. If youre not familiar with IPTables functionality and usage, then you may also want to check out some of the URLs listed at the top of the firewall scripts(HOWTOs, etc).

I hope you find these scripts useful, if you have any comments or suggestions please feel free to email me.

Script for a multi-homed firewall is an example IPTables 1.2.1 script for a dual-homed firewall.

This script has not yet been tested thoroughly on a dual-homed firewall. If you find any problems, please drop me an email.

Current versions and documentation are available at http://www.sentry.net/~obsid/IPTables/rc.scripts.dir/current/

## User-defined Chains ##

Chain KEEP_STATE
The KEEP_STATE chain holds a few rules for generic stateful packet filtering.
This chain is called from many of the INPUT/OUTPUT chains to DROP "INVALID"
and perhaps "UNCLEAN" packets and allow other packets from "RELATED" or
"ESTABLISHED" connections.

CHECK_FLAGS
The CHECK_FLAGS chain contains a few rules to filter based on TCP flags.
These rules do indeed filter mainly bogus/malicious traffic(scans, etc). It
would be a good idea to keep an eye on what these rules send to the logs.
Null scans are also logged and dropped, in the mangle table.

DENY_PORTS
The DENY_PORTS chains contains a few rules to DROP and/or LOG packets based
on the source and/or destination port number of the packet.

Packets destined to/from the following ports are dropped by default in the script. These are just some examples of some commonly used ports that certain daemons/trojans/DDoS agents may utilize.

## TCP ##
137:139 SMB
2049 NFS
6000:6063 X
20034 Netbus 2 Pro
12345:12346 Netbus
27374 SubSeven
27665,27444,31335 Trinoo
10498,12754 Mstream

## UDP ##
2049 NFS
31337 BO2k
27444,31335 Trinoo
10498 mstream

These are just examples to stare at. They guarantee no real protection against the associated trojans.

For more common port numbers check out:
http://www.sans.org/newlook/resources/IDFAQ/oddports.htm

ALLOW_PORTS
The ALLOW_PORTS chain simply ACCEPTs packets based on port number. If you have
a default FORWARD policy of DROP, then you would need to utilize a chain like
this if you are DNATing/routing connections behind the firewall or perhaps
running services on(!!!) the firewall.

ALLOW_ICMP
The ALLOW_ICMP chains simply allows packets based on ICMP type. Currently
the firewall allows the flow of the following ICMP types:
Echo Reply (pong)
Destination Unreachable
Echo Request (ping)
TTL Exceeded (traceroute)

SRC_EGRESS && DST_EGRESS
The SRC_EGRESS and DST_EGRESS chains filter packets that have a source or
destination IP address matching an array of private or reserved subnets.

TOS_OUTPUT
The TOS_OUTPUT chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of locally generated, outgoing packets.

TOS_PREROUTING
The TOS_PREROUTING chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of packets being routed through the firewall.

The following user-defined chains are pretty obvious. The firewall script is designed to have a user-defined INPUT and OUTPUT chain for every available interface. From these user-defined chains are called the user-defined chains
mentioned above, which I call "Special Chains". The chains below are then called by the built-in INPUT/OUTPUT/FORWARD chains. This isnt really the rule, of course, alot of the user-defined chains mentioned above are called directly from the built-in INPUT/OUTPUT/FORWARD chains. This is done to assure proper flow of the packets through the filters.

EXTERNAL_INPUT
INTERNAL_INPUT
DMZ_INPUT
LO_INPUT
EXTERNAL_OUTPUT
INTERNAL_OUTPUT
DMZ_OUTPUT
LO_OUTPUT