IT Questions and Answers :)

Monday, September 30, 2019

What is something that generally wouldn't help with avoiding Trojan infections on Symbian-based devices?

What is something that generally wouldn't help with avoiding Trojan infections on Symbian-based devices?

  • Upgrade your device every 12 months
  • Use mobile security software
  • Keep firmware and OS versions up to date.
  • Install only Symbian-signed or trusted programs 
What is something that generally wouldn't help with avoiding Trojan infections on Symbian-based devices?

EXPLANATION

A Trojan is a program that looks genuine but has a disruptive agenda. The motive behind designing a Trojan is to get access to data inside a person’s computer.
It gives access to your most sensitive data that may include credit card information. This is done by creating a backdoor. You can protect yourself against Trojans by downloading software and programs that come from known and verified sources, and not obtained by a random search on the Internet.

 

Share:

Which feature was first included by default in PowerShell version 5?

Which feature was first included by default in PowerShell version 5?

  • PowerShellGet
  • Desired State Configuration
  • Workflow
  • Automatic module import 
Which feature was first included by default in PowerShell version 5?


EXPLANATION

New features in Windows PowerShell Desired State Configuration

  • Windows PowerShell language enhancements let you define Windows PowerShell Desired State Configuration (DSC) resources by using classes. Import-DscResource is now a true dynamic keyword; Windows PowerShell parses the specified module’s root module, searching for classes that contain the DscResource attribute. You can now use classes to define DSC resources, in which neither a MOF file nor a DSCResource subfolder in the module folder is required. A Windows PowerShell module file can contain multiple DSC resource classes.
  • A new parameter, ThrottleLimit, has been added to the following cmdlets in the PSDesiredStateConfiguration module. Add the ThrottleLimit parameter to specify the number of target computers or devices on which you want the command to work at the same time.
    • Get-DscConfiguration
    • Get-DscConfigurationStatus
    • Get-DscLocalConfigurationManager
    • Restore-DscConfiguration
    • Test-DscConfiguration
    • Compare-DscConfiguration
    • Publish-DscConfiguration
    • Set-DscLocalConfigurationManager
    • Start-DscConfiguration
    • Update-DscConfiguration
  • With centralized DSC error reporting, rich error information is not only logged in the event log, but it can be sent to a central location for later analysis. You can use this central location to store DSC configuration errors that have occurred for any server in their environment. After the report server is defined in the meta-configuration, all errors are sent to the report server, and then stored in a database. You can set up this functionality regardless of whether or not a target node is configured to pull configurations from a pull server.
  • Improvements to Windows PowerShell ISE ease DSC resource authoring. You can now do the following.
    • List all DSC resources within a configuration or node block by entering Ctrl+Space on a blank line within the block.
    • Automatic completion on resource properties of the enumeration type.
    • Automatic completion on the DependsOn property of DSC resources, based on other resource instances in the configuration.
    • Improved tab completion of resource property values.
  • A new DscLocalConfigurationManager attribute designates a configuration block as a meta-configuration, which is used to configure the DSC Local Configuration Manager. This attribute restricts a configuration to containing only items which configure the DSC Local Configuration Manager. During processing, this configuration generates a *.meta.mof file that is then sent to the appropriate target nodes by running the Set-DscLocalConfigurationManager cmdlet.
  • Partial configurations are now allowed in Windows PowerShell 5.0. You can deliver configuration documents to a node in fragments. For a node to receive multiple fragments of a configuration document, the node’s Local Configuration Manager must be first set to specify the expected fragments
  • Cross-computer synchronization is new in DSC in Windows PowerShell 5.0. By using the built-in WaitFor* resources (WaitForAll, WaitForAny, and WaitForSome), you can now specify dependencies across computers during configuration runs, without external orchestrations. These resources provide node-to-node synchronization by using CIM connections over the WS-Man protocol. A configuration can wait for another computer’s specific resource state to change.
  • Just Enough Administration (JEA), a new delegation security feature, leverages DSC and Windows PowerShell constrained runspaces to help secure enterprises from data loss or compromise by employees, whether intentional or unintentional. For more information about JEA, including where you can download the xJEA DSC resource, seeJust Enough Administration, Step by Step.
  • The following new cmdlets have been added to the PSDesiredStateConfiguration module.
    • A new Get-DscConfigurationStatus cmdlet gets high-level information about configuration status from a target node. You can obtain the status of the last, or of all configurations.
    • A new Compare-DscConfiguration cmdlet compares a specified configuration with the actual state of one or more target nodes.
    • A new Publish-DscConfiguration cmdlet copies a configuration MOF file to a target node, but does not apply the configuration. The configuration is applied during the next consistency pass, or when you run the Update-DscConfiguration cmdlet.
    • A new Test-DscConfiguration cmdlet lets you verify that a resulting configuration matches the desired configuration, returning either True if the configuration matches the desired configuration, or False if the actual configuration does not match the desired configuration.
    • A new Update-DscConfiguration cmdlet forces a configuration to be processed. If the Local Configuration Manager is in pull mode, the cmdlet gets the configuration from the pull server before applying it.


Share:

What is the IPv6 private address range?

What is the IPv6 private address range?

  • fe80:0000:0000:0000 - feff:ffff:ffff:ffff
  • ffc0:0000:0000:0000 - ffef:ffff:ffff:ffff
  • fd00:0000:0000:0000 - fdff:ffff:ffff:ffff
  • fec0:0000:0000:0000 - feff:ffff:ffff:ffff 
What is the IPv6 private address range?


EXPLANATION

Here is a unique private IPv6 address range generated just for you (refresh page to get another one):
Prefix/L:  fd
Global ID:  2aec802d69
Subnet ID:  d701
Combined/CID:  fd2a:ec80:2d69:d701::/64
IPv6 addresses:  fd2a:ec80:2d69:d701:xxxx:xxxx:xxxx:xxxx

If you have multiple locations/sites/networks, you should assign each one a different "Subnet ID", but use the same "Global" ID for all of them.
The IPv6 address space is so huge (2128) that everyone should be able to get a public IP address for every device they will ever own. So theoretically it shouldn't be necessary to have private IPv6 addresses like the 192.168.x.x and 10.x.x.x addresses in IPv4.

However until you can actually get an IPv6 address range from your ISP, you may want to use "private" addresses for internal networks and testing etc.
In IPv6 there is a special "Unique Unicast" IP range of fc00::/7 which should be used for this as per RFC4193.
The official definition looks like this:

| 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
+--------+-+------------+-----------+----------------------------+
| Prefix |L| Global ID  | Subnet ID |        Interface ID        |
+--------+-+------------+-----------+----------------------------+
In practice such address will always start with "fd" because the 8th (L) bit must be one.
The "Global ID" and "Subnet ID" must be random to ensure uniqueness (which is what this page does).
You are free to assign addresses from the rest (Interface ID).

Please note:
A former standard proposed the use of so-called "site-local" addresses in the fec0::/10 range.
This has been deprecated (see RFC3879) and should no longer be used.

 

Share:

What does tagging a switchport for vLAN access do?

What does tagging a switchport for vLAN access do?

  • Identifies private/public network packets
  • Protects against DDoS attacks
  • Allows any vLANs to pass between switches
  • Allows correctly labeled vLAN traffic through port 

What does tagging a switchport for vLAN access do?

EXPLANATION

 If you have more than one VLAN on a port (a "trunk port"), you need some way to tell which packet belongs to which VLAN on the other end. To do this you are "tagging" a packet with a VLAN tag (or VLAN header if you like). In reality a VLAN tag is inserted in the Ethernet frame.

The 802.1Q (dot1q, VLAN) tag contains a VLAN-ID and other things explained in the 802.1Q Standard. The first 16 bits contain the "Tag Protocol Identifier" (TPID) which is 8100. This also doubles as the EtherType 0x8100 for devices that don't understand VLANs.
So a "tagged" packet contains the VLAN information in the Ethernet frame while an "untagged" packet doesn't. A typical use case would be if you have one port from a router to a switch which multiple customers
In this example customer "Green" has VLAN 10 and Customer "Blue" has VLAN 20. The ports between switch and customers are "untagged" meaning for the customer the arriving packet is just a normal Ethernet packet.
The port between router and switch is configured as a trunk port so that both router and switch know which packet belongs to which customer VLAN. On that port the Ethernet frames are tagged with the 802.1Q tag.
Share:

In networking, what does the acronym "EIGRP" stand for?

In networking, what does the acronym "EIGRP" stand for?

  • Enhanced Interior Gateway Routing Protocol
  • Enhanced Internet Gateway Routing Protocol
  • Extra Interior Gateway Routing Protocol
  • Enhanced Internet Gateway Router Protocol 
In networking, what does the acronym "EIGRP" stand for?

EXPLANATION

 Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance-vector routing protocol that is used on a computer network for automating routing decisions and configuration. The protocol was designed by Cisco Systems as a proprietary protocol, available only on Cisco routers.

Share:

Popular Posts