Free ado net data services software for linux

Firebird .NET Data Provider is an ADO.NET data provider for Firebird. Firebird .NET Data Provider is written in C# and provides a high-performance native implementation of the Firebird API. It also includes an implementation of the Firebird Services API and Firebird array datatype support.

Firebird is a relational database offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. It has been used in production systems, under a variety of names since 1981.

Firebird is a commercially independent project of C and C++ programmers, technical advisors and supporters developing and enhancing a multi-platform relational database management system based on the source code released by Inprise Corp (now known as Borland Software Corp) on 25 July, 2000 under the InterBase Public License v.1.0

PTlink IRC Services provides channel/nick registration services for IRC networks.
Specially developed for the PTlink IRC Server, it uses modules and includes features like channel roles and nick groups for privilege management.
The data backend is a MySQL database.
Enhancements:
- This version fixes a synchronization problem with user kicks, replaces some fatal errors with warnings, and updates the utility scripts to reflect the latest configuration changes.

Net::SynchroEdit::Service is a Perl extension for SynchroEdit response service functionality.

SYNOPSIS

use Net::SynchroEdit::Service;

my $conn = new Net::SynchroEdit::Service;
$conn->connect("localhost", 7962, "root", "secret");

Net::SynchroEdit::Service provides a complete set of methods for manipulating a SynchroEdit server via the response service. The optional Net::SynchroEdit::Controller and Net::SynchroEdit::Session modules can be used in conjunction with the Service module to acquire e.g. the create_from_file method (Controller).

Configuration with no services supported script is for a single host firewall configuration with no services supported by the firewall machine itself.

Sample:

# USER CONFIGURABLE SECTION

# The name and location of the ipchains utility.
IPTABLES=iptables

# The path to the ipchains executable.
PATH="/usr/local/sbin"

# Our internal network address space and its supporting network device.
OURNET="10.5.0.0/24"
OURBCAST="10.5.0.255"
OURDEV="eth0"

# The outside address and the network device that supports it.
ANYADDR="0/0"
ANYDEV="ppp0"

# The TCP services we wish to allow to pass - "" empty means all ports
# note: comma separated
TCPIN="ssh,ftp,ftp-data"
TCPOUT="smtp,www,ssh,telnet,ftp,ftp-data,irc,http"

# The UDP services we wish to allow to pass - "" empty means all ports
# note: comma separated
UDPIN="domain"
UDPOUT="domain"

# The ICMP services we wish to allow to pass - "" empty means all types
# ref: /usr/include/netinet/ip_icmp.h for type numbers
# note: comma separated
ICMPIN="0,3,11"
ICMPOUT="8,3,11"

# Logging; uncomment the following line to enable logging of datagrams
# that are blocked by the firewall.
# LOGGING=1

# END USER CONFIGURABLE SECTION
####################################
# Flush the Input table rules
echo -n Flushing forward... && {
$IPTABLES -F FORWARD
} && echo done

# We want to deny incoming access by default.
# echo -n Denying incoming access... && {
# $IPTABLES -P FORWARD drop
# } && echo done

# Drop all datagrams destined for this host received from outside.
echo -n Dropping incoming datagrams... && {
$IPTABLES -A INPUT -i $ANYDEV -j DROP
} && echo done

# SPOOFING
# We should not accept any datagrams with a source address matching ours
# from the outside, so we deny them.
echo -n Preventing spoofing... && {
$IPTABLES -A FORWARD -s $OURNET -i $ANYDEV -j DROP
} && echo done

# SMURF
# Disallow ICMP to our broadcast address to prevent "Smurf" style attack.
echo -n Preventing SMURFs... && {
$IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET -j DROP
} && echo done

# We should accept fragments, in iptables we must do this explicitly.
echo -n Accepting fragments... && {
$IPTABLES -A FORWARD -f -j ACCEPT
} && echo done

# TCP
# We will accept all TCP datagrams belonging to an existing connection
# (i.e. having the ACK bit set) for the TCP ports were allowing through.
# This should catch more than 95 % of all valid TCP packets.
echo -n Accepting valid incoming tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -d $OURNET --dports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done
echo -n Accepting valid outgoing tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -s $OURNET --sports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done

# TCP - INCOMING CONNECTIONS
# We will accept connection requests from the outside only on the
# allowed TCP ports.
echo -n Accepting incoming tcp connections on allowed ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $ANYDEV -d $OURNET --dports $TCPIN --syn -j ACCEPT
} && echo done

# TCP - OUTGOING CONNECTIONS
# We will accept all outgoing tcp connection requests on the allowed TCP ports.
echo -n Accepting outgoing traffic on allowed tcp ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $OURDEV -d $ANYADDR --dports $TCPOUT --syn -j ACCEPT
} && echo done

# UDP - INCOMING
# allow UDP datagrams in on the allowed ports and back.
echo -n Allowing UDP datagrams in on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -d $OURNET --dports $UDPIN -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -s $OURNET --sports $UDPIN -j ACCEPT
} && echo done

# UDP - OUTGOING
# We will allow UDP datagrams out to the allowed ports and back.
echo -n Allowing UDP datagrams out on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -d $ANYADDR --dports $UDPOUT -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -s $ANYADDR --sports $UDPOUT -j ACCEPT
} && echo done

# ICMP - INCOMING
# We will allow ICMP datagrams in of the allowed types.
# echo -n Allowing ICMP datagrams in of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET --icmp-type $ICMPIN -j ACCEPT
# } && echo done

# ICMP - OUTGOING
# We will allow ICMP datagrams out of the allowed types.
# echo -n Allowing ICMP datagrams out of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $OURDEV -d $ANYADDR --icmp-type $ICMPOUT -j ACCEPT
# } && echo done

# DEFAULT and LOGGING
# All remaining datagrams fall through to the default
# rule and are dropped. They will be logged if youve
# configured the LOGGING variable above.
#

# DoS
# enabling Syn-flood protection
echo -n Enabling Syn-flood protection... && {
iptables -A FORWARD -p tcp --syn -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling Furtive port scanner protection
echo -n Enabling Furtive port scanner protection... && {
iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling ping of death protection
echo -n Enabling ping of death protection... && {
iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
} && echo done


if [ "$LOGGING" ]
then
# Log barred TCP
$IPTABLES -A FORWARD -m tcp -p tcp -j LOG
# Log barred UDP
$IPTABLES -A FORWARD -m udp -p udp -j LOG
# Log barred ICMP
$IPTABLES -A FORWARD -m udp -p icmp -j LOG
fi
#
# end.

Google Data Objective-C Client provides a framework and source code that make it easy to access data through Google Data APIs.
The Google data APIs provide a simple protocol for reading and writing data on the web. Many Google services provide a Google data API.
Each of the following Google services provides a Google data API:
- Base
- Blogger
- Calendar
- Spreadsheets
- Picasa Web Albums
- Notebook
Additional services with Google data APIs that are not yet supported by the Objective-C Client Library:
- Code Search
- Google Apps Provisioning

OpenLink Virtuoso is a Virtual Database product that provides transparent real-time access to disparate data sources (ODBC, JDBC, XML, and Web Services), and transparent integration of disparate application logic (e.g. Mono ECMA-CLI and J2EE integration). OpenLink Virtuoso Universal Servers broad protocol support enables it to offer Web, File, and SQL database server functionality alongside native XML storage, and Web services platform functionality as part of a cohesive single server solution.
Virtuoso is at the core a high performance object-relational SQL database. As a database, it provides transactions, a smart SQL compiler, powerful stored procedure language with optional Java and .Net server side hosting, hot backup, SQL 99 and more. It has all major data access interfaces, as in ODBC, JDBC, ADO .Net and OLE/DB.
Virtuoso has a built-in web server which can serve dynamic web pages written in Virtuosos web page language as well as PHP, ASP .net and others. This same web server provides SOAP and REST access to Virtuoso stored procedures, supporting a broad set of WS protocols such as WS-Security, WS-Reliable Messaging and others. A BPEL4WS run time is also available as part of Virtuosos SOA suite.
Virtuoso has a built-in WebDAV? repository. This can host static and dynamic web content and optionally provides versioning. The WebDAV? repository is tested to interoperate with WebDAV? clients built into Windows XP, Mac OSX and others and makes Virtuoso a convenient and secure place for keeping ones files on the net. Further, Virtuoso provides automatic metadata extraction and full text searching for supported content types.
Open Virtuoso supports SPARQL embedded into SQL for querying RDF data stored in Virtuosos database. SPARQL benefits from low-level support in the engine itself, such as SPARQL aware type casting rules and a dedicated IRI data type. This is the newest and fastest developing area in Virtuoso.
Enhancements:
- Enhanced cost-based optimizer
- Fixed cost calculation for RDF inf nodes
- Added larger sample in query cost model sampling
- Enhanced SPARQL support
- Added BREAKUP
- Added CONSTRUCT ... LIMIT ...
- Significant performance optimizations
- Added QUAD MAP { ... } group pattern
- Updated documentation
- Significant update of all ODS applications
- Added compliance to latest SIOC vocabulary
- Added calendar
- Added OpenID login and registration
- Added new SIOC subclasses to allow RDF inference
- Enhancements to existing applications
- Bug fixes

swordcoast.net IRCd is a fork of Undernets IRCu 2.10.12 that features more possibilities for network services, less power for IRC operators, some of QuakeNets Asuka patches, more versatile host hiding, customizable whois information lines, improvements for silence masks, and a few other things.
Enhancements:
- Apart from integrating all changes made in ircu 2.10.12 and Asuka 1.2.1, this release fixes compile issues, EPITHETs, and issues with privilege propagation.
- It adds a command to adjust MAXOPLEVEL per channel, a user mode to shun people (prevent them from doing anything possibly visible to other users except services), extended host hiding (see README), and forced joins and relaying join to services as requests.

Net::DNS::TestNS is a Perl extension for simulating simple Nameservers.

SYNOPSIS

use Net::DNS::TestNS;

ABSTRACT

Class for setting up "simple DNS" servers.

Class to setup a number of nameservers that respond to specific DNS queries (QNAME,QTYPE) by prespecified answers. This class is to be used in test suites where you want to have servers to show predefined behavior.

If the server will do a lookup based on QNAME,QTYPE and return the specified data. If there is no QNAME, QTYPE match the server will return a SERVFAIL.

A log will be written to STDERR it contains time, IP/PORT, QNAME, QTYPE, RCODE