Re: [Full-Disclosure] HTMLShip encrypt

2004-09-15 Thread m . mohr
I took a quick look at the HTMLShip website. Their product does not 'encrypt' anything; rather, it obfuscates the HTML content with Javascript. Everything you need to 'decrypt' the page content is right there on the downloaded page. ___ Full-Disclos

[Full-Disclosure] followup: xor/otp

2004-09-15 Thread m . mohr
Sorry; it seems that the server I put the archive on went down shortly after I uploaded it. Here is another link: http://www.css-auth.com/xor_otp_0.60.tar.gz ___ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-chart

[Full-Disclosure] xor/otp

2004-09-14 Thread m . mohr
://www.temerity.net/~mohr/xor_otp_0.60.tar.gz ___ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html

[Full-Disclosure] Small (but useful) utility

2004-08-05 Thread M\. Mohr
When I couldn't find a decent file wiping utility on my own machine, I decided to write one. Yes, I did search the net and came up with a few... but they seem to be poorly written and overly complicated. So, in just 64 lines, I wrote one that would be useful for me, that would work well, and that

Re: [Full-Disclosure] Shaft DDOS

2004-07-31 Thread mohr
If you're gonna distribute source code, please ensure that it will compile with a modern complier!! I understand that this may have been posted as a historical document (it is dated from 2000), but really. My amateurish C isn't advanced enough to fix everything in shaftnode, but I did try to f

Re: [Full-Disclosure] Automated SSH login attempts?

2004-07-25 Thread Paul Mohr
There's a thread on DSLR about it, about 2 days old now: http://www.dslreports.com/forum/remark,10854834~mode=flat~days= -- Paul Mohr [EMAIL PROTECTED] ___ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-discl

[Full-Disclosure] full-disclosure@lists.netsys.com

2004-07-05 Thread mohr
The whole gmail flame war kind of pisses me off. This *is* full-disclosure. The people who state that flaws in beta software should not be reported here are being counter-productive to the goals of this list: release of software security holes to teh general public. If you're worried about "s

RE: [Full-Disclosure] mydoom.c information

2004-03-07 Thread m . mohr
On Sun, 7 Mar 2004, Frank Knobbe wrote: > On Sun, 2004-03-07 at 19:47, Chris Eagle wrote: > > > As I recall the -L option (persistent listener) only works on the windows > > > port. > > > > > > > If you want it for Unix: > > How about? > > while true;do nc -l -p 1234;done The problem with that

Re: [Full-Disclosure] mydoom.c information

2004-03-07 Thread m . mohr
Heh heh heh. How could I be using the Windows version if I am running Bash on Linux? :) On Sun, 7 Mar 2004, John Sage wrote: > heh.. > > On Sun, Mar 07, 2004 at 02:01:01PM -0800, [EMAIL PROTECTED] wrote: > > From: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > Subject: Re: [Full-Disclosure] my

Re: [Full-Disclosure] mydoom.c information

2004-03-07 Thread m . mohr
uld have helped me quite a bit. Although the bit about intentionally infecting oneself doesn't exactly make me want to jump for joy. > > as i do not wish to type-iterate. > > Donnie Werner > http://exploitlabs.com > In any case, thank you for your reply! Regards, Michael Mo

[Full-Disclosure] mydoom.c information

2004-03-06 Thread m . mohr
I recently read somewhere that mydoom.c included the source code for the a variant. Being the curious type, I wanted to see it. During my research, I came across a post from a professor in the same situation as I was, bascially looking for sync-src-1.00.tbz. That message was posted to this list,