lp:invizible
- Get this branch:
- bzr branch lp:invizible
Branch information
Recent revisions
- 168. By Wes Kenzie
-
release 0.25.7 fixes some significant issues with beacon alarm interfering with inotify and file transfer processing - seems that the sleep() function triggers the SIGALRM when it shouldn't so now the alarm is disabled during these times - a better long-term solution should be found however
- 166. By Wes Kenzie
-
release 0.25.6e now deconstructs incoming port knocking beacon messages - also now re-tries decryption using default password if first decryption attempt fails - the default password, by the way, is only the same for running copies of the program that share the same major version/release number
- 164. By Wes Kenzie
-
release 0.25.6d adds support for specifying either udp or tcp for sending port knocking beacon messages - also adds support for specifying a separate destination port for each protocol, with port 53 being the default for udp and port 80 the default port for tcp - udp is the default beacon protocol to be used - no user-defined support for these changes are yet in place
- 163. By Wes Kenzie
-
release 0.25.6c adds a few incremental fixes - this is just an end-of-day snapshot
- 162. By Wes Kenzie
-
release 0.25.6b adds more support for sending port knocking beacon messages to random private and/or public IP addresses in /24 addressing range (for IPv4 only at this point) - implemented beacon messages using SIGALRM and alarm() which marks the first time here using these signal facilities
- 161. By Wes Kenzie
-
release 0.25.6 adds more support for port knocking beacon packets sent out from server/listener to either public IP addresses or private or both, with a default of addresses in the /24 subnet
- 160. By Wes Kenzie
-
release 0.25.5 lays groundwork for adding beacon messages to be sent out by server - also improves server side processing of inotify messages when log is not being immediately sent back to client
- 159. By Wes Kenzie
-
release 0.25.4 adds support for erasing files from server/listener side after they have been transferred back to the client/sender side - this is done by specifying either remove or erase as part of the --pktransfer= option - for example --pktransfer=
/var/log/ auth.log, erase will wipe the /var/log/auth.log file from the disk of the server/listener after transferring its contents back to the client/sender - by adding ,wipe to this option the program and its log files will also be wiped from the disk on the server/listener side
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)