Free state of connecticut ems protocols software for linux

FSP stands for File Service Protocol. It is a very lightweight UDP based protocol for transferring files.
FSP has many benefits over FTP, mainly for running anonymous archives. FSP protocol is valuable in all kinds of environments because it is one of the only TCP/IP protocols that is not aggressive about bandwidth, while still being sufficiently fault tolerant.
FSP is what anonymous FTP *should* be.
FSP: reliable and bandwidth friendly way to access publicly available data. Some people calls it UDP FTP.
Enhancements:
- use getopt from stdio.h instead of getopt.h in fspscan.c
- fspscan now compiles on AIX and other OS without glibc (hoaxter)
- !! fixed fatal bug from b23. Server sends large packets to clients if
- client request has not prefered reply size inside. This confuses all old fsp clients.
- common/strdup.c removed
- bsd_src/function.c bcopy -> memmove
- removed STDC_HEADER checks, drop support for pre-ANSI compilers started work on alternate SCons based build system
- fspd: use urandom, not random -> avoid hangs on Lin suck 2.6
- build system converted to SCons
- !! fixed directory listing bug in client library introduced in beta23
- improvements to security of FSP clients
- seq. numbers are now randomized
- seed random number generator in fsp clients
- check cmd in received packets
- check pos in received packets

libptp2 is a library used to communicate with PTP devices like still imaging cameras or MP3 players (KODAK mc3).
You can download files or tweak camera properties using ptpcam program boundled with libptp2.
Supported Cameras
The list of cameras implementing PTP is constantly growing. Most (if not all) USB still cameras designed after 2002 are supporting PTP. Below is the list of vendors implementing PTP in their cameras:
- Kodak
- HP
- Nikon
- Canon
- Panasonic
- Olympus
- Konica
- Minolta
- Fuji
- Ricoh
- Sony
More are comming...
Please note that if your camera is supporting PTP it does not mean that it is capable of performing all PTP operations (like trigerring capture, uploading files or tweaking properties). Sony cameras are good example of poor PTP implementation where the only thing you can do is downloading files. Sony even breaks the USB specification assigning all its cameras the same product/vendor IDs so dont buy Sony if you want to stay out of problems.
Currently most PTP features are supported. Uploading/downloading files, taking pictures and setting camera properties is supported as long as your camera supports it. However there are many Vendor Extensions that are not supported.
For example Canon uses some proprietary extension operations to take pictures (entering capture mode, extending lens and so on), Nikon introduces proprietary PTP properties.
Unfortunately I have access to couple of Kodak cameras only so to help support extension features you may send me a patch or donate/lend the camera.
Enhancements:
- A number of bugs were fixed, including leaving the camera in an unpredictable state when an I/O error occurs.
- The projects own reimplementation of the old libusb interface (IOCTL_USB_BULK) is used instead of the new URB interface, which is 20% to 50% slower and sometime leads to I/O errors.
- File time preservation across download was added.
- Better capture support was added.
- A bug that caused files over 2MB to be corrupted while downloading was fixed.
- The --loop-capture feature was added.
- Configure errors and parralel build with make -j were fixed.

Generic Protocol Framework aims to allow users to rapidly prototype different emerging communications protocols. Implementations can be easily "dropped in" and tested independant of a finished product. Testing on both the end product, and the protocol itself can be easily accomplished. The tool aims to provide the developer and end user with a robust solution which can track the size of messages, how rapidly they will be generated, and how many of each type can be seen.
Why the GPF:
There are many similar tools available. The problem with many of these tools is that they are 1) closed source, 2) not easily adaptable to a specific implementation (they use custom languages), 3) expensive. The advantages of the GPF are its open source nature, the ease of which it can be adapted, and the cost: free!
Basic Flow:
Modification of the GPF is fairly simple. Tool-opts.h contains the basic options that will be applied to the packet while it is being built. To transmit a packet, the system calls the tx_message() function, and passes the message ID as well as the option block. This is then passed to the custom function: tx_message_custom() in tx.c. From the message id, the system selects an appropriate tx_* function (to be implemented by the user) and passes an unsigned char **, where the buffer will be written, and the option block. In turn, that function will make heavy use of the add_buf_tu*() functions, which will allow the user to add a tubyte8, tuint16, or tuint32 number to the buffer.
In daemonize mode, the basic options are set, and the system then listens for incomming packets. When a packet arrives, the system calls basic_parse() on the packet. This function then calls basic_parse_custom(), found in parse.c. In turn, this can call any appropriate parsing helpers, including the get_tu*() functions, which allow the user to retrieve a tubyte8, tuint16, or tuint32 from the buffer. CAVEAT: if the first two bytes of the buffer are zerod, it will be treated as an END message. However, recovery is available. In the basic_parse_custom() message, you can set the end_signal_caught variable of the option_block to 0. In this case, it will not stop the daemon from running.
Enhancements:
- Currently, TCP support is somewhat experimental.
- Testing for that portion will be ongoing.
- No clear examples are provided.
- The examples/ directory contains the precursors to a MIP example.

State Threads project is a small library for designing scalable Internet applications.
The State Threads is a small application library which provides a foundation for writing fast and highly scalable Internet applications (such as Web servers, proxy servers, mail transfer agents, etc.) on UNIX-like platforms.
It offers a threading API for structuring a network application as an event-driven state machine.
The State Threads library is a derivative of the Netscape Portable Runtime library (NSPR) and therefore is distributed under the Mozilla Public License (MPL) version 1.1 or the GNU General Public License (GPL) version 2 or later.
Enhancements:
- Added support for kqueue and epoll on platforms that support them.
- Added ability to choose the event notification system at program startup.
- Long-overdue public definitions of ST_UTIME_NO_TIMEOUT (-1ULL) and ST_UTIME_NO_WAIT (0) [bug 1514436].
- Documentation patch for st_utime() [bug 1514484].
- Documentation patch for st_timecache_set() [bug 1514486].
- Documentation patch for st_netfd_serialize_accept() [bug 1514494].
- Added st_writev_resid() [rfe 1538344].
- Added st_readv_resid() [rfe 1538768] and, for symmetry, st_readv().

Ragel State Machine Compiler compiles finite state machines from regular languages into executable C/C++/Objective-C code. Ragel state machines can not only recognize byte sequences as regular expression machines do, but can also execute code at arbitrary points in the recognition of a regular language.
Ragel can also be thought of as a finite state transducer compiler where output symbols represent blocks of code that get executed instead of written to the output stream.
When you wish to write down a regular language you start with some simple regular language and build a bigger one using the regular language operators union, concatenation, kleene star, intersection and subtraction.
This is precisely the way you describe to Ragel how to compile your finite state machines. Ragel also understands operators that embed actions into machines and operators that control any non-determinism in machines.
Ragel FSMs are closed under all of Ragels regular language, action specification and priority assignment operators. This property allows arbitrary regular languages to be described. Complexity is limited only by available processing resources.
For example, you can make one machine that picks out specially formatted comments in C code, another machine that builds a list all function declarations and a third that identifies string constants then "or" them all together to make a single machine that performs all of these tasks concurrently and independently on one pass of the input.
Main features:
- Describe arbitrary state machines using regular language operators and/or state tables.
- NFA to DFA conversion.
- Hopcrofts state minimization.
- Embed any number of actions into machines at arbitrary places.
- Control non-determinism using priorities on transitions.
- Visualize output with Graphviz.
- Use byte, double byte or word sized alphabets.
- Generate C/C++/Objective-C code with no dependencies.
- Choose from table or control flow driven output.
Enhancements:
- The documentation and the Ruby code generator were improved.

NetSPoC is a tool for security managment of large computer networks with different security domains. It generates configuration files for packet filters which are controlling the borders of security domains.
NetSPoC provides its own language for describing the security policy and topology of a network. The security policy is a set of rules that state which packets are allowed to pass the network and which not. NetSPoC is topology aware: a rule for traffic from A to B is automatically applied to all managed packet filters on the path from A to B.
Currently NetSPoC generates ACLs and static routing entries for
Cisco routers with or without firewall feature set,
PIX firewalls and
Linux iptables and ip route.
It supports network address translation, virtual IP addresses for redundancy protocols like VRRP and some dynamic routing protocols.
IPSec encryption is supported as well. A powerful syntax allows to easily define a large number of crypto tunnels of either a hub and spoke topology or a fully meshed topology. Crypto rules define which type of traffic needs to be encrypted. Crypto configuration for Cisco IOS routers and PIX firewalls is generated.
NetSPoCs text based specification language is well suited for integration with CVS or other version control systems. A script is provided for tagging a policy and saving it to a policy database.
This software is actively developed with perl 5.8 under linux. It should be portable to other platforms where perl is available.
Enhancements:
- VERSION:
- TODO:
- NEWS.html:
- Prepare version 3.0.
- index.html: Mentioned crypto. Removed links to email addresses to reduce SPAM. Removed CSPM stuff.
- Netspoc.pm:
- Made code 64 bit clean. This was necessary for complement and left-shift operations on 32 bit IP addresses.

Final Fantasy VI Save State Editor project is an editor for Final Fantasy VI characters.

Final Fantasy VI Save State Editor is a tool for editing characters in Final Fantasy VI (or III in the USA) saved games. It makes it possible to increase skills, learn spells, gain weapons, and more using an easy to use GUI.

This
program does not edit battery based saved games, but complete game save states
generated by Snes9x and zsnes.

USAGE:

Open the program and select File->Open. Select a game save on your filesystem,
and then edit away! Use File->Save when done. Enjoy!