Re: Stego for watermarking Perl5 code?

1999-03-23 Thread Jim Gillogly
"Shabbir J. Safdar" [EMAIL PROTECTED] skribis: So I'm looking to protect some Perl code from the situation where someone might break into my site and copy it and start marketing it. ... given the relatively free form nature of the language and the fact that I can throw in all sorts of

Re: bind with DNSSEC finally released

1999-03-23 Thread Donald E. Eastlake 3rd
Why didn't you just do a type=ANY query to "." and find out? The answer is, of course not. The root servers are somewhat sensitive and currently there are 13 of them because that is the maximum number you can have without overflowing DNS UDP and requiring the much higher number of packets

Re: Stego for watermarking Perl5 code?

1999-03-23 Thread Dan Geer
Shabbir, In the 70's and early 80's, I was part of a team distributing a modestly massive Fortran program that we wanted people to use but not commercialize. Our solution then, well before we all got so smart, was to convert every label, variable, subroutine name, etc., to a random sequence of

Re: references to password sniffer incident

1999-03-23 Thread William Allen Simpson
Catching up on email, I will point out that every major service provider is probably compromised to one degree or another as frequently as 3 times per year from terminal rooms. For example, in addition to Usenix meetings: IETF meetings, NANOG meetings, and every other computer meeting or show

Re: references to password sniffer incident

1999-03-23 Thread Phil Karn
Actually, things are getting much better in the IETF terminal rooms. SSH is now *very* widely used, with encrypted Telnet and IPSEC trailing well behind. Phil