Bug 214503

Summary: [NEW PORT]: security/0d1n : Web security tool to make fuzzing at HTTP inputs
Product: Ports & Packages Reporter: Rihaz Jerrin <rihaz.jerrin>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me CC: danfe, rihaz.jerrin
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
[new port ]: security/0d1n shar file
none
[new port ]: security/0d1n port file none

Description Rihaz Jerrin 2016-11-14 12:14:39 UTC 
Created attachment 176992 [details]
[new port ]: security/0d1n shar file

Web security tool to make fuzzing at HTTP
inputs.Features include Brute force 
passwords in auth forms, Directory
disclosure (use PATH list ),
Test list on input to find SQL Injection
and XSS vulnerabilities
WWW:https://github.com/CoolerVoid/0d1n
Comment 1 Rihaz Jerrin 2016-11-21 07:46:00 UTC 
Created attachment 177227 [details]
[new port ]: security/0d1n port file
Comment 2 commit-hook freebsd_committer freebsd_triage 2017-03-07 12:57:30 UTC 
A commit references this bug:

Author: danfe
Date: Tue Mar  7 12:56:36 UTC 2017
New revision: 435600
URL: https://svnweb.freebsd.org/changeset/ports/435600

Log:
  Add a port of `security/0d1n', web HTTP fuzzing tool and bruteforcer.

  Because GitHub releases (tarballs) are not fetched with correct modification
  time, set TIMESTAMP to 1484434410 which corresponds to commit 5e4e0ee tagged
  as this release.

  PR:		214503 (modified)
  Submitted by:	Rihaz Jerrin

Changes:
  head/security/0d1n/
  head/security/0d1n/Makefile
  head/security/0d1n/distinfo
  head/security/0d1n/files/
  head/security/0d1n/files/patch-Makefile
  head/security/0d1n/pkg-descr
  head/security/Makefile
Comment 3 Alexey Dokuchaev freebsd_committer freebsd_triage 2017-03-07 13:01:22 UTC 
Port was added as of ports r435600, thank you.  Notice that I've taken liberty to update it to version 2.3 and did some cleanups on the Makefile and patch.

Please try to pay attention to Porters Handbook's recommendations regarding our common practices and style next.  Running portlint(1) (install from `ports-mgmt/portlint' or via package) is also good idea prior to sending PR.