Re: [Full-Disclosure] NAT router inbound network traffic subversion

2005-01-28 Thread bart2k
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Check it here -> http://www1.cs.columbia.edu/~smb/papers/fnat.pdf This should help clarify why NAT can not be considered a security feature. On Thu, 27 Jan 2005 22:12:19 -0800 Kristian Hermansen <[EMAIL PROTECTED]> wrote: >I have Googled around and

Re: [Full-Disclosure] Re: iDEFENSE - New Tricks [web censorship!]

2004-08-13 Thread bart2k
So should we propose an amendment to the US amendment? Maybe something like "Freedom of speech. As long you say what we want hear." Concerned about your privacy? Follow this link to get secure FREE email: http://www.hushmail.com/?l=2 Free, ultra-private instant messaging with Hush

Re: [Full-Disclosure] search engine proxy

2004-06-23 Thread bart2k
you mean something like clicking on the "Cached" linked next to the URL in your google search results? On Wed, 23 Jun 2004 06:37:55 -0700 "Geo." <[EMAIL PROTECTED]> wrote: >I believe it was on this list that someone once mentioned a way to >use >either google or yahoo as a proxy server by typing i

Re: [Full-Disclosure] viruses being sent to this list

2004-03-23 Thread bart2k
- = Dude...Your mom lied your NOT special ! = - Go join another list which is moderated and protects your from yourself. On Mon, 22 Mar 2004 22:06:04 -0800 Gadi Evron <[EMAIL PROTECTED]> wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >| based on this snippet, your previous posts are bu

Re: [Full-Disclosure] Emailing SSN info

2004-03-18 Thread bart2k
First off review the Institutes Privacy Policy I'm sure you have one. Then ask "Higher" management why they are password protecting a zip file (worthless secure). Finally make a recommendation to speak with the vendor who is getting the data and ask what secure methods of transport they support

Re: [Full-Disclosure] Apache 1.3.29

2004-03-12 Thread bart2k
On Thu, 11 Mar 2004 12:38:02 -0800 VeNoMouS <[EMAIL PROTECTED]> wrote: >any one know if theres a new exploit for apache 1.3.29 in the wild >one of my mates boxes was breached this morning by ir4dex appears >they gained axx via apache then got root via mmap() Only one I have seen is for "Apache f

RE: [inbox] Re: [Full-Disclosure] Re: E-Mail viruses

2004-03-05 Thread bart2k
Curt, Please tell me that your kidding about your comment: "An alternative is to allow only a proprietary extension through, like .inc Legitimate senders would rename the file, be it .exe .doc .jpg, indicate in the body of the message what the true extension is, and the receiver merely renames

Re: [Full-Disclosure] EEYE: Microsoft ASN.1 Library Bit String Heap Corruption

2004-02-11 Thread bart2k
I for one am very grateful for the fact that eEye releases technical information on the flaw. I think it helps us ALL to know the technical information so WE as security and IT professionals have a better idea of what the real risk is. I'm sorry but Microsoft Knowledge Base KB828028 tells me noth

Re: [Full-Disclosure] January 04 MDAC patch

2004-01-23 Thread bart2k
I think what your looking for is: Microsoft Baseline Security Analyzer V1.2 which can be found at http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/Tools/MBSAhome.asp == On Fri, 23 Jan 2004 13:20:01 -0800 "Geo." <[EMAIL PROTECTED

Re: [Full-Disclosure] UTTER HORSESHIT: [was January 15 is Personal Firewall Day, help the cause]

2004-01-15 Thread bart2k
So if the point of PFW Awareness Day, is to make the average "Joe" or "Jane" more IT security aware.would we as memebers of the IT security community not do more good to have a "Complete Disclosure Day" instead of a mis-leading, tease, buy-my-product day ??? If your true intentions are to show

Re: [Full-Disclosure] Professional Groups

2004-01-13 Thread bart2k
Scratch the Union idea! I say you look toward a Professional Secret Society...I hear they were all the rage in past power-player days :) On Mon, 12 Jan 2004 12:31:03 -0800 Daniel Sichel <[EMAIL PROTECTED]> wrote: >> It's time we as a professional group start talking and walking >like >> adults (a

Re: [Full-Disclosure] gcc: Internal compiler error: program cc1 got fatal signal 11

2004-01-09 Thread bart2k
Confimed - Segmentation Fault OS = Slackware 9.1.0 Kernel = 2.4.22 GCC = 3.2.3 int main(void) { printf("%c","msux"[0xcafebabe]); } $ gcc gcc-crash.c $ ./a.out Segmentation fault Concerned about your privacy? Follow this link to get FREE encrypted email: https://www.hushmail.com/?l=2 F