22-11-2015, 11:08 #1
$3,50 VPS KVM OVH 2GB RAM 10GB SSD 100Mbps - Montreal (Canada)
Linha VPS SSD 2016 v1 - Xeon E5v3 @ 2.4 GHz
VPS SSD 1
- OpenStack KVM
- 1 vCore
- 2.4 GHz
- 2 GB RAM
- 10 GB SSD
- Local RAID 10
- $3.49 /month
VPS SSD 2
- OpenStack KVM
- 1 vCore
- 2.4 GHz
- 4 GB RAM
- 20 GB SSD
- Local RAID 10
- $6.99 /month
VPS SSD 3
- OpenStack KVM
- 2 vCores
- 2.4 GHz
- 8 GB RAM
- 40 GB SSD
- Local RAID 10
- $13.49 /month
22-11-2015, 12:37 #2
MEASURES AGAINST SPAM SENDING FROM OVH NETWORK
OVH is implementing a set of technical measures to fight against the sending for fraudulent e-mails as well of SPAM from its infrastructures.
To this end, OVH performs some verification on the traffic sent from the server used by the client to port 25 (SMTP) on the Internet. The traffic is analyzed by automatic tools .
Emails sending are neither filtered nor intercepted but checked with a time lag of a few seconds. These operations are performed in parallel and in sequentially before the emails are sent to the Internet.
Similarly, no operation is performed on the emails sent: OVH does not tag emails, and does not alter in any way the emails sent by the Client. No information is stored by OVH during these operations outside of statistics. This operation is done regularly and is fully automatic. No human intervention is performed when checking traffic to port 25 (SMTP port).
In the case of the emails sent from a Client’s server identified as spam or fraudulent, OVH will inform the Client by email and will block the SMTP server port.
OVH does not retain any copies of emails sent from the SMTP Server even when identified as spam.
The Customer may request the unblocking of the SMTP port through the management interface.
Any new email identified as spam will result in a new blocking of the SMTP port for a longer time.
From the third blocking, OVH reserves the right to refuse any request to unblock the SMTP port.
MITIGATION (PROTECTION FROM DOS AND DDOS ATTACKS)
OVH is implementing a protection against Denial Of Service (DOS) and Distributed Denial Of Service (DDOS) computer attacks and provided when made in a massive way. This feature is intended to prevent the Customer’s operations to be inaccessible during the attack.
This object of this feature is to check the traffic to the Customer’s Service and from outside of the OVH network.
The illegitimate qualified traffic is then rejected upstream in the Client’s infrastructure, allowing legitimate users to access the Service despite the undergoing cyberattack.
These safeguards do not prevent other computer attacks such as SQL injection, bruteforce, security vulnerabilities’ exploitation etc.
Due to the great complexity of this Protection Service, OVH is not subject to an obligation of means; it is possible that the attack is not detected by the tools in place, and that the tools developed do not prevent the operation of the Service to be interrupted.
Depending on the nature of the attack and its complexity, OVH deploys a protection at different levels of traffic to preserve its infrastructure and the Customer Service.
Mitigation is activated only after the attack is detected by OVH tools, and a minimum of 26 hours. Therefore until the activation of mitigation, the Service is frontally affected by the attack, which can lead to its unavailability.
As soon as the cyber attack is identified and mitigation is automatically activated, mitigation can not be disabled until the end of a 26 hours period.
Throughout the duration of the activation of mitigation, OVH can not guarantee the availability and accessibility of the Client’s applications but will try to limit the impact of this attack on Customer's Service and on OVH’s Infrastructure.
If, despite the activation of mitigation, the cyber attack is likely to jeopardize the integrity of the OVH’s or of other OVH customers, OVH will strengthen its protective measures which may cause a degradation of the Customer Service or impact its availability.
Finally, it is possible that some of the data generated by the attack can not be detected by the OVH equipment and reach the Customer Service. The effectiveness of mitigation also depends on the configuration of the Customer's Service; as such, it is up to them to verify that they have the necessary skills to ensure proper administration.
The mitigation does not exempt the Client to secure its Service, to implement security tools (firewalls ...), to regularly update its system, backup its data or to ensure the security of its computer programs (scripts, codes ...).
Última edição por 5ms; 22-11-2015 às 12:45.
23-11-2015, 10:12 #3
Painel de Controle
Reinstalando - Debian 8
De outros produtos OVH:
Information to follow = não implementado, quem sabe um dia
23-11-2015, 10:34 #4
As delicias da OVH + OpenStack
A reinstalação morreu em 58%. Todos os botões desativados.
Resta ficar olhando o capim crescer.
23-11-2015, 12:04 #5
Tela painel de controle (13:00 Brasilia):
An error occurred on reinstalling your VPS
There is a task in error in progress. Some features will be unavailable until it is resolved. Please wait a few moments.
Opened on the: 11/23/15 10:47 AM (11:47 Brasilia)
Updated on the: 11/23/15 11:35 AM
Thank you for raising your issue with OVH Support.
I have escalated the issue in order to pinpoint the problem. I apologize for
If you ever have any other questions or concerns, feel free to contact us
through ticket, or for instant phone support, through our toll-free line at
1-855-684-5463. We are there 24/7 to help you!
Thank you and have a great day!
23-11-2015, 12:11 #6
23-11-2015, 12:23 #7
Dados para acesso: Mon, 23 Nov 2015 10:48:08 -0200
Foi entregue com Debian 7, tinha encomendado Debian 8.
Não cheguei a acessar. É apenas para testes, principalmente relativos a OpenStack. "Curiosamente" não veio com endereços IPv6.
23-11-2015, 12:47 #8
13:45 liberou para reinstalação. Lá vamos nós.
23-11-2015, 12:58 #9
Morreu em 58%
Daqui a z horas, quando liberar novamente, vou tentar Debian 7.
23-11-2015, 14:31 #10
root@ca11:~# date Mon Nov 23 17:21:08 UTC 2015 root@ca11:~# uptime 17:21:08 up 11 min, 1 user, load average: 0.01, 0.03, 0.02Código:
root@ca11:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Model name: Intel Xeon E312xx (Sandy Bridge) Stepping: 1 CPU MHz: 2394.472 BogoMIPS: 4788.94 Virtualization: VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0Código:
root@ca11:~# cat /proc/version Linux version 3.16.0-4-amd64 (email@example.com) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) root@ca11:~# cat /etc/debian_version 8.2 root@ca11:~# uname -r 3.16.0-4-amd64 root@ca11:~# uname -m x86_64 root@ca11:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.2 (jessie) Release: 8.2 Codename: jessieCódigo:
root@ca11:~# free total used free shared buffers cached Mem: 2009556 200864 1808692 5296 11232 143752 -/+ buffers/cache: 45880 1963676 Swap: 0 0 0 root@ca11:~# dd if=/dev/zero of=/swap bs=32k count=64k 65536+0 records in 65536+0 records out 2147483648 bytes (2.1 GB) copied, 4.54933 s, 472 MB/s root@ca11:~# free total used free shared buffers cached Mem: 2009556 1928632 80924 5296 14372 1819388 -/+ buffers/cache: 94872 1914684 Swap: 2097148 0 2097148
root@ca11:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 9.9G 2.9G 6.6G 31% / (2GB é swap) udev 10M 0 10M 0% /dev tmpfs 393M 5.2M 388M 2% /run tmpfs 982M 0 982M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 982M 0 982M 0% /sys/fs/cgroup tmpfs 197M 0 197M 0% /run/user/0 root@ca11:~# df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda1 655360 33879 621481 6% / udev 249155 287 248868 1% /dev tmpfs 251194 291 250903 1% /run tmpfs 251194 1 251193 1% /dev/shm tmpfs 251194 3 251191 1% /run/lock tmpfs 251194 13 251181 1% /sys/fs/cgroup tmpfs 251194 4 251190 1% /run/user/0
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 2.71918 s, 395 MB/s
root@ca11:~# wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2015-11-23 17:29:57-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 220.127.116.11
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|18.104.22.168|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’
/dev/null 100%[===========>] 100.00M 12.3MB/s in 8.3s
2015-11-23 17:30:06 (12.0 MB/s) - ‘/dev/null’ saved [104857600/104857600]