honeytrap-devel Mailing List for honeytrap
Brought to you by:
honeytrap
You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(18) |
Aug
(1) |
Sep
|
Oct
|
Nov
(5) |
Dec
|
2009 |
Jan
(2) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(1) |
Nov
(1) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
From: Marcin N. <mar...@fu...> - 2011-11-26 16:14:04
|
Dear Sir or madam, make encounters a problem with the tftp plugin: ____________________________________________________ htm_tftpDownload.c: In function 'get_tftp_resource': htm_tftpDownload.c:158:55: error: variable 'sv' set but not used [-Werror=unused-but-set-variable] cc1: all warnings being treated as errors ____________________________________________________ I used the following commands to compile Honeytrap: ____________________________________________________ sudo apt-get install libnetfilter-queue-dev git clone git://git.carnivore.it/libemu.git cd libemu autoreconf -v -i ./configure --prefix=/opt/libemu sudo make install git clone git://git.carnivore.it/honeytrap.git cd honeytrap autoreconf -vi ./configure --with-stream-mon=nfq --prefix=/opt/honeytrap --with-cpuemu --with-libemu-includes=/opt/libemu/include/ --with-libemu-libraries=/opt/libemu/lib/ --enable-devmodules make (<-- breakes) sudo make install ____________________________________________________ Do you have any first aid tips? I change c-sourcefiles reluctantly. Sincerely, Marcin. |
From: Tillmann W. <til...@gm...> - 2011-11-10 21:18:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcin, > I am still able to SSH the host which runs honeytrap! Why? > Honeytrap logs this event but it seems that it does not answer it, as > default reaction would be sending '\n'. I can simply login on my host, > edit files etc... > > Stopping Honeytrap and _not_ deleting the iptables ruleset ends up with > timeouts... Therefore I guess Honeytrap performs some kind of > packet-forwarding? Since your sshd is already listening on port 22/tcp, honeytrap fails to bind to that port and hands queued SYN packets back to the kernel. The same happens for other services. If you stop honeytrap, all queued packets remain in the queue forever, hence you are not able to access affected services. Your nfqueue rule basically acts as a "drop" rule. It's probably a good idea to exclude SYN segments to ports from other services from the nfqueue rule. Hope that helps, Tillmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJOvD+yAAoJEH195S4iyWW4DoEH/A8Lrrh6AxUgu2VDZRiDrl/F xs1X1Kh61vBLPxU56gMyxWkwgihTrjZ8+aptrG8C64tjeihviD+vh2lWR+1q/80e L5BBD3LODlmUaKed+Xq9w1dCOJpBQQWUon7M/xhjtcpJkqVfQUZNmn4LZd4tcBN7 8RE7X70FbgZpzu1bGTmiXstQWI5FqiABG8nuKyTIKF+EsSHL3fbUZSRUJL4w6kNt 1NCQ5yp/MmikYKsanM6yrNlemYrbhCDDJL+SnHEZEfgDUEm5pv0FIaw/dWBXSl7U fbdvuMRAJB99DITwTUfrf9jfjG8o8u8h7Blyfud4YycAU3OS0YolTk2mNjYxhcg= =u6mm -----END PGP SIGNATURE----- |
From: Marcin N. <mar...@fu...> - 2011-11-10 14:39:17
|
Dear Honeytrap users / developers, during my use of Honeytrap I encountered the following situation: Preconditions: [*] running instance of Honeytrap using nfq, [*] iptables rulesset which forwords all packets to the queue [*] portconf_default set to "normal" (no exceptions) Obersvation: I am still able to SSH the host which runs honeytrap! Why? Honeytrap logs this event but it seems that it does not answer it, as default reaction would be sending '\n'. I can simply login on my host, edit files etc... Stopping Honeytrap and _not_ deleting the iptables ruleset ends up with timeouts... Therefore I guess Honeytrap performs some kind of packet-forwarding? Sincerely, Marcin. |
From: Marcin N. <mar...@fu...> - 2011-10-13 11:57:52
|
> Dear sir or madam, > > > > my honeytrap-logfile exceeds 2GB. Therefore Honeytrap cannot log any new > entries/events. My log level is -t 5, as recommended by many sources. > > Starting honeytrap produces following error message: >> Error while writing logfile: File to large > > Where do I find the possibility to change maximum logfile size? > I appended some lines to the log, to see whether this is an OS limitation. But this worked with vim... Now im receiving the following Error Message: > Error - Unable to open logfile /opt/honeytrap/honeytrap.log: Value too large for defined data type. Writing into a (>2GB)file without data type .log ending fails, too. Sincerely, Marcin. |
From: Tillmann W. <til...@gm...> - 2011-10-11 11:53:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Marcin, > my honeytrap-logfile exceeds 2GB. Therefore Honeytrap cannot log any new > entries/events. My log level is -t 5, as recommended by many sources. > > Starting honeytrap produces following error message: >> Error while writing logfile: File to large > > Where do I find the possibility to change maximum logfile size? Most likely a file system issue. Rotate the log file or change to a file system that supports bigger files. Tillmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEbBAEBAgAGBQJOlC4iAAoJEH195S4iyWW4pmcH938q4vOgwZnDwa6bV/f/Kse1 bsOBlzmlMFywSt/2G78nM22841ha3i0ehL6NxgkW+7k2/I59cThA5xJRHLwOMXMG o0i7GSJOnmGdC++7q8KhVx/B8is5DEz4gT+NX+RWvMRmEhmcyEmYYgTEP/GuMUPQ XWOtK8YpRfhNvxMpr1VE+t2DL8FMZ/FLKC7NbT17NdUXSc6xm18g0VEGxCoY3WgY wl9N+M0RRFsOhZTMI893v0f6eJ9KyF+8f3ZWly1VHr0mhNZ1kxyCsGtrYZQcKj9p 64rwi2/DUrd9pXjAK1IFnXb9MceB3uokjvAAOlxozV6wrhYE379aFtOd2wMvsA== =iCVg -----END PGP SIGNATURE----- |
From: Marcin N. <mar...@fu...> - 2011-10-11 10:49:20
|
Dear sir or madam, my honeytrap-logfile exceeds 2GB. Therefore Honeytrap cannot log any new entries/events. My log level is -t 5, as recommended by many sources. Starting honeytrap produces following error message: > Error while writing logfile: File to large Where do I find the possibility to change maximum logfile size? Thanks, Marcin. |
From: Gary <ga...@ey...> - 2011-08-19 21:57:37
|
On Fri, Aug 19, 2011 at 4:13 AM, Marcin Nawrocki < mar...@fu...> wrote: > So there is no chance of setting up / controlling a honeytrap-testbed > which listens on _ALL_ ports, as long as I dont have any physical Access. > Am I right? > You could run it as a virtual and use some sort of virtual console for access (e.g. VirtualBox, VMware ESXi, Xen, KVM, QEMU, etc.) It might just be easier to run SSH on a random high port (e.g. somewhere between 50000-65355) and restrict access so that only certain IPs can reach it. Have you considered using something like honeystick or honeywall instread of or in addition to honeytrap? http://www.ukhoneynet.org/research/honeystick-howto http://projects.honeynet.org/honeywall -Gary |
From: Marcin N. <mar...@fu...> - 2011-08-19 11:13:13
|
So there is no chance of setting up / controlling a honeytrap-testbed which listens on _ALL_ ports, as long as I dont have any physical Access. Am I right? > Only one TCP port may be assigned at a time. So you can either run SSH on > a free port other than 22 or connect by some other method. |
From: Gary <ga...@ey...> - 2011-08-19 02:08:52
|
Only one TCP port may be assigned at a time. So you can either run SSH on a free port other than 22 or connect by some other method. |
From: Marcin N. <mar...@fu...> - 2011-08-18 15:05:58
|
Dear Sir or Madam, I am running my Honeytrap-testbed on an Ubuntu server, to which I donot own any physical access. Honeytrap handels right now all ports but SSH (22). This port ist used to configure / access this machine remotely. Is it possible, to run Honeytrap also listening on SSH port, without loosing my connectivity to this machine? Are some special configuration steps required? Regards, Marcin |
From: Tillmann W. <til...@gm...> - 2011-08-16 06:53:00
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcin, > Without the "sudo" Honeytrap cannot work properly, as it would not be able > to log into the logfile. Though started with sudo, I receive the following > failure during runtime: > > "SaveFile error - Unable to save attack string in attacks directory: > Permission denied" honeytrap requires root privileges in order to bind to well-known ports and also to receive connection requests. You can tell it to drop privileges and run connection handlers under an unprivileged user after these tasks have been completed, and my guess would be that this is what causes the problem in your case. If you do so, you have to make sure that the log file is writable also for this unprivileged user. Hope that helps. Tillmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEbBAEBAgAGBQJOShPFAAoJEH195S4iyWW47isH+LRE1ErT2jxCbAIUksr+f0W3 j05G7X920JaPXduoZ5FlaXSDfD3FkxeyzcRA/sL+N5mSnqliIO16iOnnd3blVnQW j8O5Fma24HhgdioYzeBd84MWoB5qa7OgbyNtM9zmTz553/itIqal+TqxPd3whnEp Kzjqqseg/kNjxuby/xJTiP5hgWygO2JoAiw2CMYctft3+1hRBqeNZBPggby7nA+E 0n/+1NU6FVJ+28JS0im4k3PLPe+TiwCMe3noR5jxbfbHQ40ah5juPvY3m7qNWtDV etM90pA5Kjm7QM4R8pMfqL/6tYpUrGjMINV4RIIsLx1bIj7dRS9mhVNH3Yg5Qw== =Qn3w -----END PGP SIGNATURE----- |
From: Marcin N. <mar...@fu...> - 2011-08-15 15:10:27
|
Dear Sir or Madam, I guess this question is rather easy to answer, though i would like to have an "official" validation. I have installed honeytrap into /opt/honeytrap and launch the application with: sudo /opt/honeytrap/sbin/honeytrap -C /opt/honeytrap/etc/honeytrap/honeytrap.conf -t 5 -D Without the "sudo" Honeytrap cannot work properly, as it would not be able to log into the logfile. Though started with sudo, I receive the following failure during runtime: "SaveFile error - Unable to save attack string in attacks directory: Permission denied" So please instruct me, which AccessRights shall I set? (I guess sudo is not required / anticipated?) Regards, Marcin. |
From: Stein E. G. <ste...@gm...> - 2010-01-30 21:26:15
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ./configure --help: ... - --with-magicpe store attack data in PostgreSQL database ... If I'm not mistaken, the note is wrong. Regards Stein Erik Gullvik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktko+AACgkQIx+MdL75im0bpgCgqh96U38ghugz7TsTqD0SUJQE XYMAoJZuqBOiFdOdq1iaWYpQZ1nZFDyG =rOc4 -----END PGP SIGNATURE----- |
From: Tillmann W. <til...@gm...> - 2009-11-04 10:04:30
|
Stein, > I've made a new patch that incorporates both libclamav <0.9.5 and >=0.9.5 > (with conditional compiling) > > The easiest solution for the time being is to patch htm_ClamAV.c with > enclosed patch. Thanks for the patch. I would, however, not copy the whole functions but rather use the #ifdef condition checks for the affected code parts only. Following your suggestions, I added support for the new ClamAV API to the module: <http://svn.carnivore.it/changeset/2116> Let me know what you think. Thanks, Tillmann |
From: Stein E. G. <ste...@gm...> - 2009-10-28 00:59:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've made a new patch that incorporates both libclamav <0.9.5 and >=0.9.5 (with conditional compiling) The easiest solution for the time being is to patch htm_ClamAV.c with enclosed patch. (In 'src/modules' dir do 'patch < pathtopatch' It will require a re-compile if you upgrade/ downgrade across ver 0.9.5 It would be helpful to add a note to INSTALL or README to let user know that if they have compiled against one version and are upgrading/ downgrading libclamav it will lead to Honeytrap error and abortion. I did try to add runtime check of installed libclamav, but I run into problems with module loading. I don't have more time at the moment to troubleshoot this, so it will have to wait until another time. Regards Stein Erik -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrnl3cACgkQIx+MdL75im3e6wCggiEJWSfaMBOx+4kV3jnWE6I9 YRQAn2GCucQP7N2s9qwmXDhmhI0N66mU =3PfB -----END PGP SIGNATURE----- |
From: Stein E. G. <ste...@ne...> - 2009-09-23 11:18:36
|
Update on >=libclamav-0.95 API issue. ------------------------------------ Tillmann Your proposal seems like the easiest fix, albeit a hack. I was tinkering with the idea of using configure to check for installed version and do blunt ln -s to the right htm_ClamAV.c, but that would be even more "ugly" :-) Regards Stein Erik Tillmann Werner skrev: > Hi Stein, > >> There is in fact a version function in clamav.h >> It returns software version and level (?), see line 201 in >> /usr/include/clamav.h > > Yes, I know, but that lets you determine the version during runtime > only. What we need is a method that works during compile time. I > addressed that question on the clamav-devel mailing list. Edwin Török > proposed to use a constant that is only defined for the new API, like > CL_INIT_DEFAULT. > > #ifdef CL_INIT_DEFAULT > // ... code for 0.95+ API > #else > // .. code for <0.95 API > #endif > > Although this is a hack and not perfect, I guess it's the only possible > solution so far. Let me know what you think. > > Thanks, > Tillmann > > PS.: Do you want to move this thread back to the mailing list so that > others could participate as well? Or rather stay private? Up to you. :) > |
From: Stein E. G. <ste...@ne...> - 2009-09-23 11:11:59
|
Hello all I've observed that 199 bytes attack strings (port 139) are not dumped to a file. It seems like the plugins deunicode and base64 are started several times. The child sends signal 17 after httpDownload: file save and spamsum not started. Have you seen this before?? Regards Stein Erik Gullvik |
From: Tillmann W. <til...@gm...> - 2009-09-20 10:01:46
|
HI Stein, > Here is a patch to htm_ClamAV.c which incorporates the new api in > libclamav (>=0.95) As far as I can see, you ported the code to the new API. That solves the problem with linking against newer versions of libclamav, but makes the code incompatible with older versions, which are still shipped with many distributions. What we need is a portable way to determine the version number of libclamav and choose the right API based on this info. Unfortunately, it seems like clamav.h does not contain version information. As I am currently not aware of a portable solution, I am going to address that point on the clamav mailing list. Maybe they have an advice. Thanks, Tillmann |
From: Stein E. G. <ste...@ne...> - 2009-09-18 18:53:16
|
Here is a patch to htm_ClamAV.c which incorporates the new api in libclamav (>=0.95) My build system: Ubuntu 9.04 libclamav: 0.95.2+dfsg-4ubuntu1.1 Honeytrap-svn Possible issues: Not tested on virus sample via API Regards Stein Erik Gullvik |
From: Stein E. G. <ste...@ne...> - 2009-09-15 20:33:54
|
Tillmann, I've been looking into changing the module htm_ClamAV to follow libclamav >= 0.95 I'm no great C programmer, bear this is mind when you browse my changes :-) >From 0.95 Clamav changed the api requiring a rewrite of htm_ClamAV. See https://wiki.clamav.net/Main/UpgradeNotes095 Chapter 6 in http://www.clamav.net/doc/latest/clamdoc.pdf So far I've stripped (tried to anyway) all libclamav reference in htm_ClamAV. Please have a look at enclosed file to verify that no stray code exists. My modified htm_CLamaAV compiles and runs, but I've not tested it extensively. The next step will be to import the new api. Regards Stein Erik Gullvik |
From: Tillmann W. <til...@gm...> - 2009-09-13 18:22:09
|
Hi, many thanks for the report. > I saw in the archives that there had been som issues compiling honeytrap > on Ubuntu with clamav support. I don't know if those bugs got fixed. > Anyway I experienced similar bugs the other day. Make stops with errors > when I try to add clamav support. > > I've compiled honeytrap on ubuntu before with clamav support. Possible > there are some mismatch in a recent clamav release. Which version of honeytrap are you referring to? If you haven't done so already, please try building from a clean subversion checkout. The subversion tree compiles without problems on Ubuntu 8.10. libclamav and libclamav-dev are 0.94.dfsg.2-1ubuntu0.5. As your versions are more recent, I assume you are on a more recent Ubuntu version as well. Compilation also fails for the latest official ClamAV version 0.95.2. It seems like they changed their library interface from one minor release to another. I am open to patches that extend the module to also work with new libclamav versions. If anybody wants to port the code, please do, and I will happily include it. Anyways, if you don't really need the ClamAV plugin, you may leave it out and scan downloaded files off-line. It is generally a good idea to perform expensive analysis steps like virus scans outside the sensor. Thanks, Tillmann |
From: Stein E. G. <ste...@gm...> - 2009-09-13 17:45:10
|
Hello I saw in the archives that there had been som issues compiling honeytrap on Ubuntu with clamav support. I don't know if those bugs got fixed. Anyway I experienced similar bugs the other day. Make stops with errors when I try to add clamav support. I've compiled honeytrap on ubuntu before with clamav support. Possible there are some mismatch in a recent clamav release. Regards Stein Erik Gullvik ./configure --with-efence --with-stream-mon=nfq --with-spamsum --with-clamav Here are my dev/ lib packages for clamav libclamav-dev: 0.95.1+dfsg-1ubuntu1 libclamav6: 0.95.1+dfsg-1ubuntu1 Here the debug output for make: Considering target file `htm_ClamAV.la'. File `htm_ClamAV.la' does not exist. Considering target file `htm_ClamAV.lo'. File `htm_ClamAV.lo' does not exist. Looking for an implicit rule for `htm_ClamAV.lo'. Trying pattern rule with stem `htm_ClamAV'. Trying implicit prerequisite `htm_ClamAV.c'. Found an implicit rule for `htm_ClamAV.lo'. Considering target file `htm_ClamAV.c'. Looking for an implicit rule for `htm_ClamAV.c'. Trying pattern rule with stem `htm_ClamAV'. Trying implicit prerequisite `htm_ClamAV.w'. Trying pattern rule with stem `htm_ClamAV.c'. Trying implicit prerequisite `htm_ClamAV.c,v'. Trying pattern rule with stem `htm_ClamAV.c'. Trying implicit prerequisite `RCS/htm_ClamAV.c,v'. Trying pattern rule with stem `htm_ClamAV.c'. Trying implicit prerequisite `RCS/htm_ClamAV.c'. Trying pattern rule with stem `htm_ClamAV.c'. Trying implicit prerequisite `s.htm_ClamAV.c'. Trying pattern rule with stem `htm_ClamAV.c'. Trying implicit prerequisite `SCCS/s.htm_ClamAV.c'. Trying pattern rule with stem `htm_ClamAV'. Trying implicit prerequisite `htm_ClamAV.w'. Looking for a rule with intermediate file `htm_ClamAV.w'. Avoiding implicit rule recursion. Trying pattern rule with stem `htm_ClamAV.w'. Trying implicit prerequisite `htm_ClamAV.w,v'. Trying pattern rule with stem `htm_ClamAV.w'. Trying implicit prerequisite `RCS/htm_ClamAV.w,v'. Trying pattern rule with stem `htm_ClamAV.w'. Trying implicit prerequisite `RCS/htm_ClamAV.w'. Trying pattern rule with stem `htm_ClamAV.w'. Trying implicit prerequisite `s.htm_ClamAV.w'. Trying pattern rule with stem `htm_ClamAV.w'. Trying implicit prerequisite `SCCS/s.htm_ClamAV.w'. No implicit rule found for `htm_ClamAV.c'. Finished prerequisites of target file `htm_ClamAV.c'. No need to remake target `htm_ClamAV.c'. Finished prerequisites of target file `htm_ClamAV.lo'. Must remake target `htm_ClamAV.lo'. /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../ -Wall -Werror -g -O2 -c -o htm_ClamAV.lo htm_ClamAV.c Putting child 0x0931c5d8 (htm_ClamAV.lo) PID 11949 on the chain. Live child 0x0931c5d8 (htm_ClamAV.lo) PID 11949 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../ -Wall -Werror -g -O2 -c htm_ClamAV.c -fPIC -DPIC -o .libs/htm_ClamAV.o cc1: warnings being treated as errors htm_ClamAV.c: In function ‘plugin_unload’: htm_ClamAV.c:67: error: implicit declaration of function ‘cl_free’ htm_ClamAV.c: In function ‘load_clamdb’: htm_ClamAV.c:117: error: passing argument 2 of ‘cl_load’ from incompatible pointer type htm_ClamAV.c:124: error: implicit declaration of function ‘cl_build’ htm_ClamAV.c:132: error: invalid application of ‘sizeof’ to incomplete type ‘struct cl_limits’ htm_ClamAV.c:133: error: invalid use of undefined type ‘struct cl_limits’ htm_ClamAV.c:134: error: invalid use of undefined type ‘struct cl_limits’ htm_ClamAV.c:135: error: invalid use of undefined type ‘struct cl_limits’ htm_ClamAV.c: In function ‘clamscan’: htm_ClamAV.c:186: error: passing argument 5 of ‘cl_scandesc’ makes integer from pointer without a cast htm_ClamAV.c:186: error: too many arguments to function ‘cl_scandesc’ make[4]: *** [htm_ClamAV.lo] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Reaping losing child 0x0931c5d8 PID 11949 Removing child 0x0931c5d8 PID 11949 from chain. make[4]: Leaving directory `/home/stein/Skrivebord/honeytrap/honeytrap-svn/src/modules' Reaping losing child 0x081715c0 PID 11107 Removing child 0x081715c0 PID 11107 from chain. make[3]: Leaving directory `/home/stein/Skrivebord/honeytrap/honeytrap-svn/src/modules' Reaping losing child 0x08cee8e8 PID 11101 Removing child 0x08cee8e8 PID 11101 from chain. make[2]: Leaving directory `/home/stein/Skrivebord/honeytrap/honeytrap-svn/src' Reaping losing child 0x08e124a0 PID 11093 Removing child 0x08e124a0 PID 11093 from chain. make[1]: Leaving directory `/home/stein/Skrivebord/honeytrap/honeytrap-svn' Reaping losing child 0x08c109c0 PID 11092 Removing child 0x08c109c0 PID 11092 from chain. |
From: Tillmann W. <til...@gm...> - 2009-04-30 09:43:33
|
Hi, > What's up with honeytrap.mwcollect.org? > Will it come back up online? The site is currently being migrated to honeytrap.carnivore.it. Some pages aren't up yet, but this will be the new location. Tillmann |
From: Stein E. G. <ste...@ne...> - 2009-04-29 18:52:55
|
Hi everyone What's up with honeytrap.mwcollect.org? Will it come back up online? Regards Stein Erik Gullvik |
From: Armin G. <sai...@gm...> - 2009-04-15 20:58:05
|
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>o<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< BugCON Security Conferences 2009 Mexico City, June 24-26 CALL FOR PAPERS www.bugcon.org >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>o<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< BugCON is a purely technical convention where all security researchers can show their research, projects and ideas. The main topics for BugCON '09 are: * Software security * Web security * Trojan, worm and viri development * Fuzzing * AI applications related with security * Database hacking * Privacy issues * Mobile technologies * Hardware/firmware and embedded systems hacking * Cracking and protections on software * Academic security research * Firewalls, IDS and other network hardware/software (implementation, configuration and evasion) * Open Source projects * Videogame consoles, T.V. systems, and other friki stuff * Cryptography and steganography BugCON for this edition only accepts participation in the form of conference, with a duration of 1 to 2 hours (if you need more time BugCON can offer work tables for continuing your talk); the conference language can be spanish (prefereably) or english. Remeber that BugCON is totally uncensored, so the public can start a discussion about your conference, and it's totally acceptable. BugCON has two lines, “white hat” topic and “black hat” topic the technical reviewers going to collocate your conferences in the most adecuate clasification. BugCON reserves the right to accept or reject any paper. All proposals should be sent to sec...@bu... with a little description about the conference and a little curriculum about the author, from March 17th to April 30th (no extensions). The final schedule will be published on May 18th. Once your conference is accepted you should send a confirmation, a telephone number for contacting you and details about your arrival. |