Skip to content

Commit a146e1b

Browse files
jonasbardinojonasbardino
committed
Merge remote-tracking branch 'origin/master' into edge
2 parents 88b4d8b + eba299f commit a146e1b

File tree

4 files changed

+46
-43
lines changed

4 files changed

+46
-43
lines changed

‎state/wwwpublic/support-erda.dk.html

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -543,7 +543,7 @@ <h4 class="staticpage">Why do I get "Account disabled or expired" emails?</h4>
543543
ERDA account access can also just continue with their usual web
544544
login before their I/O service logins.
545545
</p>
546-
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SSHFS?</h4>
546+
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SFTP/SSHFS?</h4>
547547
<p>
548548
That error message is a common symptom of a firewall ban at ERDA. We
549549
experience regular password guessing attacks and rely on a self-defense
@@ -554,7 +554,7 @@ <h4 class="staticpage">What's the cause of "read: Connection reset by peer" erro
554554
The ban period depends on the login pattern and simple repeated
555555
password failures usually only result in a 15 minute ban. More
556556
aggressive scans and failures on the other hand may trigger a 24 hour
557-
ban, while the most blatant cracking attempts result in a 24 day ban.<br/>
557+
ban, while the most blatant cracking attempts result in a 10 day ban.<br/>
558558
For multi-user systems and computers behind a shared gateway these bans
559559
unfortunately may result in not only the offender but also several
560560
other users or computers getting affected by the ban. In the sense that
@@ -563,8 +563,8 @@ <h4 class="staticpage">What's the cause of "read: Connection reset by peer" erro
563563
Thus, please contact us on
564564
ERDA support if you hit this issue and it remains so even after 15
565565
minutes without further login attempts.<br/>
566-
If you include the public IP address that you connect from
567-
(<a href="https://ip.me">ip.me</a>) it's a significant help to
566+
If you include the public IP address that you connect from
567+
(<a href="https://ip.me">ip.me</a>) it's a significant help to
568568
investigate and getting any unnecessary bans lifted without further delay.
569569
</p>
570570
<h4 class="staticpage">Can I get an ERDA account without a UCPH account?</h4>
@@ -1047,19 +1047,19 @@ <h4 class="staticpage">Hvorfor modtager jeg "Account disabled or expired" emails
10471047
kan ligeledes blot ufortrødent fortsætte med at logge ind på web
10481048
inden deres I/O-service logins.
10491049
</p>
1050-
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SSHFS?</h4>
1050+
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SFTP/SSHFS?</h4>
10511051
<p>
10521052
Fejlbeskeden er typisk et symptom på firewall-blokering på ERDA. Vi
10531053
oplever jævnligt automatiserede forsøg på at gætte kodeord fra mørke
10541054
afkroge af internettet og benytter et selvforsvars-system til at
10551055
overvåge og handle når det ser tegn på mulige angreb eller misbrug.<br/>
10561056
I praksis blokerer det automatisk IP-adresser midlertidigt når vi
1057-
modtager for mange fejlede login-forsøg over en givet tidsrum.
1057+
modtager for mange fejlede login-forsøg over en givet tidsrum.<br/>
10581058
Blokeringens varighed afhænger af login-mønsteret så simple gentagne
10591059
forkerte kodeord typisk kun fører til en 15 minutters blokering. Mere
10601060
ihærdige skanninger eller systematiske gæt fører derimod til en
10611061
24-timers blokering, mens der ved oplagte ondsindede angreb blokeres i
1062-
24 dage.<br/>
1062+
10 dage.<br/>
10631063
For flerbrugersystemer og computere bag en delt gateway kan
10641064
blokeringerne uheldigvis føre til at ikke kun synderen, men også
10651065
adskillige andre brugere eller computere bliver berørt. D.v.s. spærret

‎state/wwwpublic/support-migrid.org.html

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -399,7 +399,7 @@ <h4 class="staticpage">Why do I get "Account disabled or expired" emails?</h4>
399399
MiGrid account access can also just continue with their usual web
400400
login before their I/O service logins.
401401
</p>
402-
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SSHFS?</h4>
402+
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SFTP/SSHFS?</h4>
403403
<p>
404404
That error message is a common symptom of a firewall ban at MiGrid. We
405405
experience regular password guessing attacks and rely on a self-defense
@@ -410,16 +410,17 @@ <h4 class="staticpage">What's the cause of "read: Connection reset by peer" erro
410410
The ban period depends on the login pattern and simple repeated
411411
password failures usually only result in a 15 minute ban. More
412412
aggressive scans and failures on the other hand may trigger a 24 hour
413-
ban, while the most blatant cracking attempts result in a 24 day ban.<br/>
413+
ban, while the most blatant cracking attempts result in a 10 day ban.<br/>
414414
For multi-user systems and computers behind a shared gateway these bans
415415
unfortunately may result in not only the offender but also several
416416
other users or computers getting affected by the ban. In the sense that
417417
they are no longer able to reach MiGrid until the ban expires or gets
418418
manually lifted by the site administrators.<br/>
419-
Thus, please contact us on MiGrid support if you hit this issue and
420-
it remains so even after 15 minutes without further login attempts.<br/>
421-
If you include the public IP address that you connect from
422-
(<a href="https://ip.me">ip.me</a>) it's a significant help to
419+
Thus, please contact us on
420+
MiGrid support if you hit this issue and it remains so even after 15
421+
minutes without further login attempts.<br/>
422+
If you include the public IP address that you connect from
423+
(<a href="https://ip.me">ip.me</a>) it's a significant help to
423424
investigate and getting any unnecessary bans lifted without further delay.
424425
</p>
425426
<h4 class="staticpage">Can I use a certifcate to access MiGrid?</h4>
@@ -743,27 +744,28 @@ <h4 class="staticpage">Hvorfor modtager jeg "Account disabled or expired" emails
743744
ufortrødent fortsætte med at logge ind på web inden deres I/O-service
744745
logins.
745746
</p>
746-
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SSHFS?</h4>
747+
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SFTP/SSHFS?</h4>
747748
<p>
748749
Fejlbeskeden er typisk et symptom på firewall-blokering på MiGrid. Vi
749750
oplever jævnligt automatiserede forsøg på at gætte kodeord fra mørke
750751
afkroge af internettet og benytter et selvforsvars-system til at
751752
overvåge og handle når det ser tegn på mulige angreb eller misbrug.<br/>
752753
I praksis blokerer det automatisk IP-adresser midlertidigt når vi
753-
modtager for mange fejlede login-forsøg over en givet tidsrum.
754+
modtager for mange fejlede login-forsøg over en givet tidsrum.<br/>
754755
Blokeringens varighed afhænger af login-mønsteret så simple gentagne
755756
forkerte kodeord typisk kun fører til en 15 minutters blokering. Mere
756757
ihærdige skanninger eller systematiske gæt fører derimod til en
757758
24-timers blokering, mens der ved oplagte ondsindede angreb blokeres i
758-
24 dage.<br/>
759+
10 dage.<br/>
759760
For flerbrugersystemer og computere bag en delt gateway kan
760761
blokeringerne uheldigvis føre til at ikke kun synderen, men også
761762
adskillige andre brugere eller computere bliver berørt. D.v.s. spærret
762763
fra at kunne forbinde til MiGrid indtil blokeringen enten udløber eller
763764
manuelt fjernes af en administrator.<br/>
764765
Kontakt os derfor venligst på
765766
MiGrid-support hvis du oplever blokering og det ikke er gået væk efter 15
766-
minutter uden yderligere login-forsøg. Hvis du medsender den offentlige
767+
minutter uden yderligere login-forsøg.<br/>
768+
Hvis du medsender den offentlige
767769
IP-adresse du forbinder fra (se <a href="https://ip.me">ip.me</a>) er
768770
det en væsentlig hjælp til at vi hurtigst muligt kan undersøge sagen og
769771
fjerne evt unødvendige blokeringer.

‎state/wwwpublic/support-sif.erda.dk.html

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -363,7 +363,7 @@ <h4 class="staticpage">What about timely removal of GDPR data, the right to rect
363363
previous backups if possible or more likely just refuse to restore any
364364
copies of the data from backup earlier than that point in time.
365365
</p>
366-
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SSHFS?</h4>
366+
<h4 class="staticpage">What's the cause of "read: Connection reset by peer" errors e.g. for SFTP/SSHFS?</h4>
367367
<p>
368368
That error message is a common symptom of a firewall ban at SIF. We
369369
experience regular password guessing attacks and rely on a self-defense
@@ -374,7 +374,7 @@ <h4 class="staticpage">What's the cause of "read: Connection reset by peer" erro
374374
The ban period depends on the login pattern and simple repeated
375375
password failures usually only result in a 15 minute ban. More
376376
aggressive scans and failures on the other hand may trigger a 24 hour
377-
ban, while the most blatant cracking attempts result in a 24 day ban.<br/>
377+
ban, while the most blatant cracking attempts result in a 10 day ban.<br/>
378378
For multi-user systems and computers behind a shared gateway these bans
379379
unfortunately may result in not only the offender but also several
380380
other users or computers getting affected by the ban. In the sense that
@@ -383,10 +383,9 @@ <h4 class="staticpage">What's the cause of "read: Connection reset by peer" erro
383383
Thus, please contact us on
384384
SIF support if you hit this issue and it remains so even after 15
385385
minutes without further login attempts.<br/>
386-
If you include the public IP
387-
address that you connect from (<a href="https://ip.me">ip.me</a>) it's
388-
a significant help to investigate and getting any unnecessary bans
389-
lifted without further delay.
386+
If you include the public IP address that you connect from
387+
(<a href="https://ip.me">ip.me</a>) it's a significant help to
388+
investigate and getting any unnecessary bans lifted without further delay.
390389
</p>
391390
<h4 class="staticpage">Can I get or keep a SIF account without a UCPH account?</h4>
392391
<p>
@@ -712,20 +711,19 @@ <h4 class="staticpage">Hvordan med rettidig sletning af GDPR-data, retten til be
712711
eller mere sandsynligt bare at afvise eventuelle anmodninger om at
713712
genskabe sikkerhedskopier af filerne fra en ældre dato.
714713
</p>
715-
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SSHFS?</h4>
714+
<h4 class="staticpage">Hvad er årsagen til "read: Connection reset by peer" fejl f.eks. med SFTP/SSHFS?</h4>
716715
<p>
717716
Fejlbeskeden er typisk et symptom på firewall-blokering på SIF. Vi
718717
oplever jævnligt automatiserede forsøg på at gætte kodeord fra mørke
719718
afkroge af internettet og benytter et selvforsvars-system til at
720719
overvåge og handle når det ser tegn på mulige angreb eller misbrug.<br/>
721720
I praksis blokerer det automatisk IP-adresser midlertidigt når vi
722721
modtager for mange fejlede login-forsøg over en givet tidsrum.<br/>
723-
<br/>
724722
Blokeringens varighed afhænger af login-mønsteret så simple gentagne
725723
forkerte kodeord typisk kun fører til en 15 minutters blokering. Mere
726724
ihærdige skanninger eller systematiske gæt fører derimod til en
727725
24-timers blokering, mens der ved oplagte ondsindede angreb blokeres i
728-
24 dage.<br/>
726+
10 dage.<br/>
729727
For flerbrugersystemer og computere bag en delt gateway kan
730728
blokeringerne uheldigvis føre til at ikke kun synderen, men også
731729
adskillige andre brugere eller computere bliver berørt. D.v.s. spærret

0 commit comments

Comments
 (0)