Stop Brute Force / Dictionary Attacks Download Brutelock Download the Open Source Brutelock program. This download provides both real-time protection against brute force/dictionary attacks using the Brutelock daemon, as well as includes the sync program to grab updates from the Brutelock subscription service. System Requirements Currently Brutelock runs on most Linux distributions with iptables and can be downloaded, installed and running in less than 2 minutes! The Brutelock agent requires the following libraries: libxml2 sqlite3 libcurl How to Install Install from source There are just a few steps to install the Brutelock agent: Download Brutelock agent, and save to /usr/local/ cd /usr/local/ tar -xjvf brutelock-version_number.tar.bz2 cd /usr/local/brutelock-version_number . Don't forget to get your subscription key to make full use of the Brutelock service! Using Brutelock with other scripts The Brutelock subscription service can also be accessed via other locking scripts and programs.
An introduction to git-svn for Subversion/SVK users and deserter This article is aimed at people who want to contribute to projects which are using Subversion as their code-wiki . It is particularly targeted at SVK users, who are already used to a work-flow that involves disconnected operation, though this is a tiny subset of the workflows supported by the git suite. Subversion users can skip SVK and move straight onto git-svn with this tutorial. People who are responsible for Subversion servers and are converting them to git in order to lay them down to die are advised to consider the one-off git-svnimport , which is useful for bespoke conversions where you don't necessarily want to leave SVN/CVS/etc breadcrumbs behind. I'll mention bespoke conversions at the end of the tutorial, and the sort of thing that you end up doing with them. This is quite different from the Git - SVN Crash Course on the Git home page, which is intended for people who are familiar with Subversion who want to work with Git mastered projects using Git. Sam Vilain Contents: What!?
Git - SVN Crash Course Welcome to the Git version control system! Here we will briefly introduce you to Git usage based on your current Subversion knowledge. You will need the latest Git installed; There is also a potentially useful tutorial in the Git documentation. This page is not maintained anymore! The up-to-date version of this tutorial is the GitSvnCrashCourse page at the Git wiki. How to Read Me In those small tables, at the left we always list the Git commands for the task, while at the right the corresponding Subversion commands you would use for the job are listed. Before running any command the first time, it's recommended that you at least quickly skim through its manual page. Things You Should Know There are couple important concepts it is good to know when starting with Git. Repositories. Commiting For the first introduction, let's make your project tracked by Git and see how we get around to do daily development in it. Now your tree is officially tracked by Git. That's it. Browsing Merging
Rails API with the AJAX flavor Commodore 64 Online User Manual Det här domännamnet är köpt och parkerat av en kund till oss. Om du vill ta reda på den publika ägar- och kontaktinformationen kan du använda tjänsten LoopiaWHOIS. Vid registrering av domännamn hos oss ingår tjänsten LoopiaDomän helt utan kostnad. För ytterligare information om vår domäntjänst LoopiaDNS, vänligen besök vår hemsida på adressen www.loopia.se. I LoopiaDNS ingår nedanstående tjänster: Vidarebefordring av WWW. Domäner till alla. Attraktiva priser på attraktiva domäntyper. Ingen hemsida? Vad är väl en domän utan en hemsida? Starta hemsida, webbutik eller blogg med ett klick. Autotrace : Vectorisation d'image Bienvenue Invité vous devez vous enregistrer pour pouvoir poster un message. Avec identifiant, mot de passe et durée de la session Le monde du Libre » Vidéo » Tutoriaux vidéo » Sujet: Autotrace : Vectorisation d'image Autotrace : Vectorisation d'image Juin 23, 2005, 16:26:27 Krysteen Kraong Kan Administrateur Karma: 3 Messages: 331 autotrace [options] inputfile Les options les plus importantes sont : -color-count : entier compris entre 0 - 256. Bonjour, Autotrace est un outil de vectorisation d'image bien pratique pour les graphistes, qui a le mérite d'être portable sur Linux et Windows et d'être sous licence GNU GPL.
git-svn(1) git svn <command> [options] [arguments] git svn is a simple conduit for changesets between Subversion and git. It provides a bidirectional flow of changes between a Subversion and a git repository. git svn can track a standard Subversion repository, following the common "trunk/branches/tags" layout, with the --stdlayout option. It can also follow branches and tags in any layout with the -T/-t/-b options (see options to init below, and also the clone command). Once tracking a Subversion repository (with any of the above methods), the git repository can be updated from Subversion by the fetch command and Subversion updated from git by the dcommit command. svn.noMetadata svn-remote. This gets rid of the git-svn-id: lines at the end of every commit. This option can only be used for one-shot imports as git svn will not be able to fetch again without metadata. The git svn log command will not work on repositories using this, either. svn.useSvmProps svn-remote. svn.useSvnsyncProps svn-remote.
Tv's cobweb: Git for Computer Scientists Abstract Quick introduction to git internals for people who are not scared by words like Directed Acyclic Graph. Storage In simplified form, git object storage is "just" a DAG of objects, with a handful of different types of objects. blob: The simplest object, just a bunch of bytes. tree: Directories are represented by tree object. When a node points to another node in the DAG, it depends on the other node: it cannot exist without it. commit: A commit refers to a tree that represents the state of the files at the time of the commit. refs: References, or heads or branches, are like post-it notes slapped on a node in the DAG. git commit adds a node to the DAG and moves the post-it note for current branch to this new node. The HEAD ref is special in that it actually points to another ref. remote refs: Remote references are post-it notes of a different color. tag: A tag is both a node in the DAG and a post-it note (of yet another color). History This is the simplest repository.
Perl programming documentation SCRIPTS D'UNE LIGNE UTILES POUR SED (ÉDITEUR DÉFILANT UNIX) Git User's Manual (for version 1.5.3 or newer) This chapter covers internal details of the git implementation which probably only git developers need to understand. It is not always easy for new developers to find their way through Git’s source code. This section gives you a little guidance to show where to start. A good place to start is with the contents of the initial commit, with: $ git checkout e83c5163 The initial revision lays the foundation for almost everything git has today, but is small enough to read in one sitting. Note that terminology has changed since that revision. Also, we do not call it "cache" any more, but rather "index"; however, the file is still called cache.h. If you grasp the ideas in that initial commit, you should check out a more recent version and skim cache.h, object.h and commit.h. In the early days, Git (in the tradition of UNIX) was a bunch of programs which were extremely simple, and which you used in scripts, piping the output of one into another. Next step: get familiar with the object naming. Voila.
Setting up a cloned git repo I was going to set up a clone of the xserver git repo in my people.freedesktop.org home directory and I figured I'd document the steps. If you want the cheat sheet just skip to the last couple of paragraphs. First of all, to set up a repo I need ssh access to people.freedesktop.org, but since I was going to put the repo in my home directory there, I already have that. Now, the official git repos are read only mounted on /git, so the obvious thing to do is to say krh@annarchy:~$ git clone --bare /git/xorg/xserver.git xserver.git Initialized empty Git repository in /home/krh/xserver.git/ ... krh@annarchy:~$ du -sh xserver.git/ 24M xserver.git/ Most of this space is in the objects representing the files, directories and commits of the project history. krh@annarchy:~$ du -sh /git/xorg/xserver.git/ 135M /git/xorg/xserver.git/ But given that both repos are on the same filesystem, we can ask git clone to share the underlying objects. krh@annarchy:~$ touch xserver.git/git-daemon-export-ok
Packet sniffing Create a virtual promiscuous interface Edit /etc/network/interfaces: iface eth1 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down Then use `ifup eth1` to bring up the interface. The problem with this is that it may still dirty the network by sending some packets (in response to ARP and ICMP and the like). Create undetectable interface Untested! # Set the interface MAC address so that it is invalid # even if it does send out a packet (which it shouldn't). # Turn on promiscuous mode. ifconfig eth0 hw ether 00:00:00:00:00:00 promisc # Bring up the interface and ignore ARP. ifconfig eth0 -arp up ARP can also be disabled via `sysctl`. echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_ignore You can permanently set this by editing /etc/sysctl.conf: net.ipv4.conf.eth0.arp_ignore = 1 Create a virtual wifi monitor mode interface iw dev wlan0 interface add wlan0-mon type monitor ifconfig wlan0-mon up Packet Sniffing Tools ipaudit or