Changes

Template:Security guidelines (view source)

Revision as of 14:40, 28 January 2020

No change in size , 14:40, 28 January 2020

→‎RUT2xx security features

Line 373: Line 373:

<td>SSH Access Secure</td>

−

<td>By default, device allows a maximum of 5 login attempts (user defined). If all attempts are used, device will block SSH ~~acccess~~ from that source.</td>

+

<td>By default, device allows a maximum of 5 login attempts (user defined). If all attempts are used, device will block SSH access from that source.</td>

</tr>

<tr>

<td>WebUI Access Secure</td>

−

<td>By default, device allows a maximum of 5 login attempts (user defined). If all attempts are used, device will block WebUI ~~acccess~~ from that source.</td>

+

<td>By default, device allows a maximum of 5 login attempts (user defined). If all attempts are used, device will block WebUI access from that source.</td>

</tr>

<tr>

Line 395: Line 395:

<td>Pre-uplouded</td>

−

<td>Root CA certificate are only needed if you want to use HTTPS for your services. There is a default file already preloaded in this device which will be ~~overwriten~~ by any uploaded file.</td>

+

<td>Root CA certificate are only needed if you want to use HTTPS for your services. There is a default file already preloaded in this device which will be overwritten by any uploaded file.</td>

</tr>

<td>Universal Plug and Play</td>

Line 402: Line 402:

<td>UPnP doesn't require any sort of authentication from the user. Any application running on your computer in LAN can ask the router to forward a port over UPnP, which is why the malware can abuse UPnP. Recommendation - If you don’t use it when leave it not installed or turned off.</td>

</tr>

−

<td>Universal Asynchronous Receiver – ~~Transmiter~~</td>

+

<td>Universal Asynchronous Receiver – Transmitter</td>

<td> By router admin password</td>

Justinasm

0

edits