Automation in the context of multifactor authentication: Difference between revisions

Automation in the context of multifactor authentication (view source)

396 bytes added , 7 months ago

no edit summary

Bureaucrats, cc_docs_admin, cc_staff

2,306

edits

@@ Line 16: / Line 16: @@
 === <code>from="pattern-list"</code> === <!--T:5-->
-This constraint specifies that the key can only be used from IP addresses that match the patterns. This is to ensure that this key is not used from computers other than the ones intended. The patterns list must include only IP addresses that fully specify at least the network class, the network, and the subnet, which are the first 3 sections of an IP address, for example, <code>192.168.*.*</code> would not be accepted, but <code>192.168.1.*</code> would be accepted.
+This constraint specifies that the key can only be used from IP addresses that match the patterns. This is to ensure that this key is not used from computers other than the ones intended. The patterns list must include only IP addresses that fully specify at least the network class, the network, and the subnet, which are the first 3 sections of an IP address, for example, <code>192.168.*.*</code> would not be accepted, but <code>192.168.1.*</code> would be accepted. Note that the IP address should be a ''public'' IP address, thus anything like <code>10.0.0.0 – 10.255.255.255</code>, <code>172.16.0.0 – 172.31.255.255</code> and <code>192.168.0.0 – 192.168.255.255</code> would be incorrect. You can use a site like [https://whatismyipaddress.com/ What Is My IP Address?] or the shell command <code>curl ifconfig.me</code> to learn your public IP address.
 === <code>command="COMMAND"</code> === <!--T:6-->