greymouse: Вроде как речь шла о сертах, выданных после 21 октября.
Yes, you are right about that date. Unfortunately, some of my certificates issed before that date was also banned by Chrome (works in Firefox, however).
Google says it reserves the right to fully distrust all of WoSign’s certs in future releases. Adding a sense of urgency to the situation, Whalley adds that in some instances, WoSign and StartCom customers may find their certificates don’t work at all in Chrome 56.
Вроде как речь шла о сертах, выданных после 21 октября.
Yes, you are right about that date. Unfortunately, some of my certificates issed before that date was also banned by Chrome (works in Firefox, however).
https://threatpost.com/google-to-distrust-wosign-startcom-certs-in-2017/121709/
P.S. See also https://habrahabr.ru/post/325300/
StartSSL & WoSign RIP
Да должен, бота гугла он без проблем пропускает. Но вот с яндексом проблемы
/ru/forum/958512
https://www.google.com/dfp
https://www.adfox.ru/ru/
https://www.revisium.com/ai/
https://cloud.google.com/compute/docs/faq#where_can_i_find_short_product_name_ip_ranges
Вся соль в том, что такой договор у меня есть
Which contract?
https://www.copyright.ru/ru/documents/avtorskoe_pravo/peredacha_avtorskih_prav/
Replace * with $SRCDIR
It's because the files started with "." are hidden, so tar cfz xxx * will not work.
Replace it with tar cfz xxx $SRCDIR
Do online game with cash winnings. Take your %%