forum.wfido.ru  

Вернуться   forum.wfido.ru > Прочие эхи > RU.FIDONET.DIGEST

Ответ
 
Опции темы Опции просмотра
  #1  
Старый 25.01.2023, 11:42
Vladimir Fyodorov
Guest
 
Сообщений: n/a
По умолчанию FTSC_PUBLIC: Перестал открываться ftsc.org

Vladimir Fyodorov написал(а) к All в Jan 23 10:32:36 по местному времени:


> Работавший 23 года сайт FTSC http://www.ftsc.org внезапно перестал
> открываться. Радует, что у Алексея Виссарионова есть свежий бэкап.

=============================================================================
* Area : FTSC_PUBLIC
* From : Wilfred van Velzen, 2:280/464 (24 Января 2023 11:45)
* To : deon
* Subj : ftsc.org problem
=============================================================================
Нi deon,

On 2023-01-24 21:22:00, you wrote to me:

de> I was going to refresh my memory from the standards, but it seems that
de> ftsc.org has not been renewed and now replaced by a common parked
de> page?

Something seems wrong indeed. I get a blank page, but that is because my add blockers filter out all the sh*t. ;-)
When I look at the source I indeed see a lot of javascript and some 'parking-lander' urls...
=============================================================================


=============================================================================
* Area : FTSC_PUBLIC
* From : Alexey Vissarionov, 2:5020/545 (24 Января 2023 22:11)
* To : Wilfred van Velzen
* Subj : ftsc.org problem
=============================================================================
de>> I was going to refresh my memory from the standards, but it seems
de>> that ftsc.org has not been renewed and now replaced by a common
de>> parked page?
WvV> Something seems wrong indeed. I get a blank page, but that is
WvV> because my add blockers filter out all the sh*t. ;-) When I
WvV> look at the source I indeed see a lot of javascript and some
WvV> 'parking-lander' urls...

Something was changed today, 2023-01-24 08:03:25 UTC:

% whois ftsc.org | grep 2023
Updated Date: 2023-01-24T08:03:25Z

The A record was set to the address 34.160.209.102 (IPv4 only, duh), which belongs to some completely distrusted entity:

NetRange: 34.128.0.0 - 34.191.255.255
CIDR: 34.128.0.0/10
NetName: GOOGL-2
NetНandle: NET-34-128-0-0-1
Parent: NET34 (NET-34-0-0-0-0)
NetType: Direct Allocation
Organization: Google LLC (GOOGL-2)

I don't know (and, honestly, don't care) who has access to edit the NS zone
contents, but this change looks unwise.

Anyway, I have a fresh backup :-)
=============================================================================

--- GoldED+/OSX 1.1.5-b20220504
Ответить с цитированием
Ответ

Опции темы
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.

Быстрый переход


Текущее время: 15:00. Часовой пояс GMT +4.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc. Перевод: zCarot