1/1 
|
Did opencores.org get compromised? RESOLVED
by Unknown on Jul 27, 2004 |
Not available! | ||
|
Did opencores.org get compromised? No. Just that our secondary dns server
dns.secondary.org doesn't work very well these days (it seemed to work OK for several months and it seemed it got compromised by someone who wanted to direct all trafic from secondary.org managed domain names ;-). I'd suggest people to stay away from secondary.org and come up with their own secondary dns server. I removed dns.secondary.org as secondary dns for opencores.org. regards, Damjan |
|||
|
Did opencores.org get compromised? RESOLVED
by bporcella on Jul 27, 2004 |
bporcella
Posts: 22 Joined: Jan 16, 2004 Last seen: Oct 2, 2007 |
||
|
Hi.
I'm sure glad some of you all understand what is going on out there..... but for those dumb ASIC designers (like me)
who care about the site -and hope
to continue using it........ What precisely should we do? Should we start using IP numbers?
bj Porcella
http://pages.sbcglobal.net/bporcella/
----- Original Message -----
From: "Damjan Lampret" damjanl at opencores.org>
To: "Discussion list about free open source IP cores" cores at opencores.org>
Sent: Monday, July 26, 2004 8:12 PM
Subject: Re: [oc] Did opencores.org get compromised? RESOLVED
Did opencores.org get compromised? No. Just that our secondary dns server
dns.secondary.org doesn't work very well these days (it seemed to work OK
for several months and it seemed it got compromised by someone who wanted to
direct all trafic from secondary.org managed domain names ;-). I'd suggest
people to stay away from secondary.org and come up with their own secondary
dns server. I removed dns.secondary.org as secondary dns for opencores.org.
regards,
Damjan
_______________________________________________
http://www.opencores.org/mailman/listinfo/cores
|
|||
|
Did opencores.org get compromised? RESOLVED
by Unknown on Jul 27, 2004 |
Not available! | ||
|
Hi !
Use http://193.189.173.98/ only if http://www.opencores.org/ does not work.
But I think in a few hours there shouldn't be any more problems. The issue
with secondary dns server has been resolved - but it will take a day for
some your your name servers to clear their caches.
In general use of IP is not good because there is no guarantee that the site
will not change its IP address. In fact it might happen in the not so
distant future that the site will change IP address. So don't make any links
to IP address on third party web sites.
regards,
Damjan
----- Original Message -----
From: "bporcella" bporcella at sbcglobal.net>
To: "Discussion list about free open source IP cores" cores at opencores.org>
Sent: Tuesday, July 27, 2004 7:52 AM
Subject: Re: [oc] Did opencores.org get compromised? RESOLVED
Hi.
I'm sure glad some of you all understand what is going on out there..... but for those dumb ASIC designers (like me)
who care about the site -and hope
to continue using it........ What precisely should we do? Should we start using IP numbers?
bj Porcella
http://pages.sbcglobal.net/bporcella/
----- Original Message -----
From: "Damjan Lampret" damjanl at opencores.org>
To: "Discussion list about free open source IP cores"
cores at opencores.org>
Sent: Monday, July 26, 2004 8:12 PM
Subject: Re: [oc] Did opencores.org get compromised? RESOLVED
> Did opencores.org get compromised? No. Just that our secondary dns
server
> dns.secondary.org doesn't work very well these days (it seemed to work
OK
> for several months and it seemed it got compromised by someone who
wanted to
> direct all trafic from secondary.org managed domain names ;-). I'd
suggest
> people to stay away from secondary.org and come up with their own
secondary
> dns server. I removed dns.secondary.org as secondary dns for
opencores.org.
>
> regards,
> Damjan
>
>
>
> _______________________________________________
> http://www.opencores.org/mailman/listinfo/cores
_______________________________________________
http://www.opencores.org/mailman/listinfo/cores
|
|||
1/1