I have some questions that people who are no IANALs might be able to answer. It's all related to software patents, not "real" patents.
- A patent granted by the USPTO does that mean that the patent is valid only in the USA or all over the world?
- Does a patent granted by the USPTO mean that the software I make available outside the USA can't be obtained by people inside the USA? (point of sale: outside the USA)
- If people inside the USA obtain my software from a source outside the USA, are they in conflict with the law and what can be the consequences for them?
- If I'm taken to a local (non-USA) court for it, what should be the ruling about it?
- What will happen if I arrive in the USA? Can I be taken to court for these things?
1. Write a popular mail client which automatically executes arbitrary code. 2. Sue the people who hijack PCs via the above mentioned mail client. 3. Profit!
The enemy of my enemy is my friend... I feel confused.
I think the trick is to use simpler hardware, which is easy to replace.
Take todays computer: motherboard with one big black chip, CPU on it, network card also one chip on it, videocard is too impossible to figure out how it works. Due to the integrated design, you can't fix it if it is broken. And in five years you won't be able to replace it one-on-one.
On older hardware (8 bitters), you were able to repair it yourself because you knew how it worked and you know you were capable of replacing a failing chip. Even if you didn't have exactly the same chip, you can use one of a newer family which did the same but would be capable of switching much much faster.
That was not the reason. The reason is that there is more than one Perl version out right now (5.0, 5.6, 5.8) and that different people need different versions. So to get rid of this, Perl is removed from the base-system and if you need whatever-version of perl, install it via the ports system. Much more flexible.
Lately, I have been looking into different bulk data storage options available to a common man. My work depends on generating, storing and analyzing a large amount of data -- averaging about 1 TB per month.
Wrong assumption, 1 TB per month is not a common man problem.
; <<>> DiG 9.2.3 <<>> @nsauth1.bit.nl nlwhitelist.dnsbl.bit.nl axfr ;; global options: printcmd nlwhitelist.dnsbl.bit.nl. 86400 IN SOA nsauth1.bit.nl. hostmaster.bit.nl. 2004060701 28800 7200 604800 86400 nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth1.bit.nl. nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth2.bit.nl. nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth3.bit.nl. 2.0.0.127.nlwhitelist.dnsbl.bit.n l. 86400 IN A 127.0.0.2 133.103.125.129.nlwhitelist.dnsbl.bit.n l. 86400 IN A 127.0.0.2 133.103.125.129.nlwhitelist.dnsbl.bit.n l. 86400 IN TXT "Customer SMTP for Exsilia" 188.103.125.129.nlwhitelist.dnsbl.bit.nl . 86400 IN A 127.0.0.2 188.103.125.129.nlwhitelist.dnsbl.bit.n l. 86400 IN TXT "Customer SMTP for Exsilia" 90.224.7.145.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2 90.224.7.145.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Planet" 129.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2 129.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Budgetel" 27.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2 27.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Budgetel" 28.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2 28.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Budgetel"
What went wrong: "Interpreted small bushes as enormous rocks and repeatedly backed away from them."
Lesson learned: "Get new sensors that can distinguish between bush and rock."
This is how a toddler learns: bushes do budge, rocks don't budge. Except for the ones which looks like bushes but are made of rocks. Pushing the bush and see if it gives way, that's a good way to see if it is a rock or a bush. Then decide if you want to fall on it or not.
Slashdot Mirror
The "Play It Safe in Cyber Space" campaign will culminate with a four-page comic book
It's sad that they only could come up with four pages, but that's what you have to limit yourself to if you have to deal with the post-MTV generation!
http://www.bsdcan.org/
Aparthaide -> Apartheid
I have a 512/128 ADSL and pay AU$ 110.- per month for it. I'm living in Cronulla, Southern Sydney.
Except for the 175 ms lag time for overseas sites, it's all very similar and affordable.
You forgot the "netcraft confirms" and the comments of the people leaving the perl-project.
Is there oil at Papua - New Guinea?
With the risk of being non-funny: yes.
And the Australian government is making sure that they're getting their 'fair' share of it!
I have some questions that people who are no IANALs might be able to answer. It's all related to software patents, not "real" patents.
- A patent granted by the USPTO does that mean that the patent is valid only in the USA or all over the world?
- Does a patent granted by the USPTO mean that the software I make available outside the USA can't be obtained by people inside the USA? (point of sale: outside the USA)
- If people inside the USA obtain my software from a source outside the USA, are they in conflict with the law and what can be the consequences for them?
- If I'm taken to a local (non-USA) court for it, what should be the ruling about it?
- What will happen if I arrive in the USA? Can I be taken to court for these things?
Anyway, enough questions
-1 Redundant: see all previour porn-postings :-)
But that doesn't explain the missing refid...
The EkkoBSD team leader announced the project's premature death
Did somebody get a confirmation from Netcraft about this?
with xntpd:
server 127.0.0.1, port 123
stratum 4, precision -29, leap 00
refid 10.10.10.3 delay 0.00021, dispersion 0.00000 offset 0.000060
rootdelay 0.06087, rootdispersion 0.00815, synch dist 0.03857
reference time: c4a447e8.ad0b0118 Sun, Jul 18 2004 10:50:48.675
originate timestamp: c4a447f6.fc5989a7 Sun, Jul 18 2004 10:51:02.985
transmit timestamp: c4a447f6.fc4b6794 Sun, Jul 18 2004 10:51:02.985
With openntpd:
server 127.0.0.1, port 123
stratum 2, precision 0, leap 00
refid 0.0.0.0 delay 0.00024, dispersion 0.00000 offset 0.000072
rootdelay 0.00000, rootdispersion 0.00000, synch dist 0.00000
reference time: c4a49a92.575967ff Sun, Jul 18 2004 16:43:30.341
originate timestamp: c4a49c58.7acd9fff Sun, Jul 18 2004 16:51:04.479
transmit timestamp: c4a49c58.7ac07fae Sun, Jul 18 2004 16:51:04.479
It doesn't show me the refid and it doesn't the correct stratum. Any idea why not?
Can somebody test it under VMWare3?
Last time it looked promising but it hung very fast after looking promising.
1. Write a popular mail client which automatically executes arbitrary code.
2. Sue the people who hijack PCs via the above mentioned mail client.
3. Profit!
The enemy of my enemy is my friend...
I feel confused.
I think the trick is to use simpler hardware, which is easy to replace.
Take todays computer: motherboard with one big black chip, CPU on it, network card also one chip on it, videocard is too impossible to figure out how it works. Due to the integrated design, you can't fix it if it is broken. And in five years you won't be able to replace it one-on-one.
On older hardware (8 bitters), you were able to repair it yourself because you knew how it worked and you know you were capable of replacing a failing chip. Even if you didn't have exactly the same chip, you can use one of a newer family which did the same but would be capable of switching much much faster.
A Unix OS really doesn't need Perl.
That was not the reason. The reason is that there is more than one Perl version out right now (5.0, 5.6, 5.8) and that different people need different versions. So to get rid of this, Perl is removed from the base-system and if you need whatever-version of perl, install it via the ports system. Much more flexible.
Edwin
I typically hate being FORCED to register to use a web site.
Nobody is forcing you to look at the information.
But if you need the information, you have to play by the rules of the provider.
Lately, I have been looking into different bulk data storage options available to a common man. My work depends on generating, storing and analyzing a large amount of data -- averaging about 1 TB per month.
Wrong assumption, 1 TB per month is not a common man problem.
At best, they could come up with a combination that produces the same hash as the one given to them.
That's good enough for comparing encrypted passwords.
I was expecting they had a massive listing of known "legitimate" servers worldwide.
Well that's not really needed since they're only monitoring the dutch IP space, so they only need the mail servers in that IP space.
It's in the FAQ at http://virbl.bit.nl/faq.php
n l. 86400 IN A 127.0.0.2n l. 86400 IN A 127.0.0.2n l. 86400 IN TXT "Customer SMTP for Exsilia"l . 86400 IN A 127.0.0.2n l. 86400 IN TXT "Customer SMTP for Exsilia". 86400 IN TXT "Customer SMTP for Budgetel"
[~] edwin@k7>dig @nsauth1.bit.nl nlwhitelist.dnsbl.bit.nl axfr
; <<>> DiG 9.2.3 <<>> @nsauth1.bit.nl nlwhitelist.dnsbl.bit.nl axfr
;; global options: printcmd
nlwhitelist.dnsbl.bit.nl. 86400 IN SOA nsauth1.bit.nl. hostmaster.bit.nl. 2004060701 28800 7200 604800 86400
nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth1.bit.nl.
nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth2.bit.nl.
nlwhitelist.dnsbl.bit.nl. 86400 IN NS nsauth3.bit.nl.
2.0.0.127.nlwhitelist.dnsbl.bit.
133.103.125.129.nlwhitelist.dnsbl.bit.
133.103.125.129.nlwhitelist.dnsbl.bit.
188.103.125.129.nlwhitelist.dnsbl.bit.n
188.103.125.129.nlwhitelist.dnsbl.bit.
90.224.7.145.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2
90.224.7.145.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Planet"
129.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2
129.50.82.146.nlwhitelist.dnsbl.bit.nl
27.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2
27.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Budgetel"
28.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN A 127.0.0.2
28.50.82.146.nlwhitelist.dnsbl.bit.nl. 86400 IN TXT "Customer SMTP for Budgetel"
What went wrong: "Interpreted small bushes as enormous rocks and repeatedly backed away from them."
Lesson learned: "Get new sensors that can distinguish between bush and rock."
This is how a toddler learns: bushes do budge, rocks don't budge. Except for the ones which looks like bushes but are made of rocks. Pushing the bush and see if it gives way, that's a good way to see if it is a rock or a bush. Then decide if you want to fall on it or not.
From: http://www.arkko.com/ioccc.htmlo urs/COMPLEMENTS/DOC/www.ioccc.org/2000/jarijyrki.c o urs/COMPLEMENTS/DOC/www.ioccc.org/2000/Makefile
E xternal files: http://www.formation.jussieu.fr/ars/2000-2001/C/co urs/COMPLEMENTS/DOC/www.ioccc.org/2000/sheet1.info
./jarijyrki sheet1.info
Size of source code: 1,536 bytes
Source: http://www.formation.jussieu.fr/ars/2000-2001/C/c
Makefile: http://www.formation.jussieu.fr/ars/2000-2001/C/c
Usage: make jarijyrki;
end-to-end digital media experience
Connect me from the computer directly into my brain and start pressing the keys on the synthesizer!
What if you were using a brute force method? Wouldn't 000000 be a logical place to start?
Aha, so to make the brute force attack as difficult as possible they should have used 999999.