Risk of committing IdentityFile name for OpenSSH configuration to public repository

What is the risk of committing the IdentityFile line for each of my Host entries in my ~/.ssh/config to my public dotfiles repository? Would providing such information make it any easier for an attacker to compromise those keys?

cat ~/.ssh/config Host SE   Hostname security.stackexchange.com   User rage   IdentityFile ~/.ssh/security_key 

Versus

IdentityFile ~/.ssh/id_rsa 

Note: this is the default key name when invoking ssh-keygen.

Regarding Database mail configuration in sql server web edition 2012

I have enabled the database mail and sql agent service both and just to test whether the database mail is working or not, i configured the database mail, created the profile and account along with all the required details like (server name, display name, port, ssl, basic authentication) however when i tried to send test email and i am getting error in the server logs that is “unable to send mail because of the mail server (failure sending email)” something like that. I have checked the server name thrice and it is absolutely correct. Please suggest what am i doing wrong. Any help would be greatly appreciaated.

Note:- The same configuration i am using in enterprise edition and it is working perfectly fine. I am able to get the test email.

Ubuntu Server SSH configuration file help

This is my sshd_config file settings I can connect to my server with my pc using public key but I can also connect from another pc with the password of sudo user account. How can make the login possible only with public key in SSH and SFTP? Thanks a lot

# This is the sshd server system-wide configuration file.  See # sshd_config(5) for more information.  # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin  # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented.  Uncommented options override the # default value.  #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress ::  #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_ecdsa_key #HostKey /etc/ssh/ssh_host_ed25519_key  # Ciphers and keying #RekeyLimit default none  # Logging #SyslogFacility AUTH #LogLevel INFO  # Authentication:  LoginGraceTime 1m PermitRootLogin without-password #StrictModes yes MaxAuthTries 3 #MaxSessions 10  PubkeyAuthentication yes  # Expect .ssh/authorized_keys2 to be disregarded by default in future. #AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2  #AuthorizedPrincipalsFile none  #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody  # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes  # To disable tunneled clear text passwords, change to no here! PasswordAuthentication no PermitEmptyPasswords no  # Change to yes to enable challenge-response passwords (beware issues with # some PAM modules and threads) ChallengeResponseAuthentication no  # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no  # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes #GSSAPIStrictAcceptorCheck yes #GSSAPIKeyExchange no  # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication.  Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. UsePAM no  #AllowAgentForwarding yes #AllowTcpForwarding yes #GatewayPorts no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes PrintMotd no #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS no #PidFile /var/run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none  # no default banner path #Banner none  # Allow client to pass locale environment variables AcceptEnv LANG LC_*  # override default of no subsystems Subsystem   sftp    /usr/lib/openssh/sftp-server  # Example of overriding settings on a per-user basis #Match User anoncvs #   X11Forwarding no #   AllowTcpForwarding no #   PermitTTY no #   ForceCommand cvs server 

How to Troubleshoot an Error Occurred During Port Configuration

An error occurred during port configuration is one of the most common error on Windows 10 while using a printer. This error message shows up when the user presses the Configure Ports button while tweaking port settings. The error can prevent you from making changes to the Ports settings of your printer. If you are also facing the same error message on your device, then you come to the right place.
 
Source: https://mcafeecomactivate334980539.wordp…iguration/

Read Previous blog: How to Fix Netflix Error NW-2-5?

mcafee.com/activate | mcafee.com/activate

AD CS Configuration Using Install-AdcsCertificationAuthority Cmdlet

I am trying to configure a subordinate CA using a .PFX file with PowerShell. I am using the below parameters:

$  params = @{     CAType = "EnterpriseSubordinateCA"     Credential = $  credential     CertFile = C:\PKI\MyCert.pfx     CertFilePassword = $  password } Install-AdcsCertificationAuthority @params -Whatif  What if: Certification authority will be installed with the following properties: CAType: EnterpriseSubordinateCA ... ... CryptoProviderName: RSA#Microsoft Software Key Storage Provider HashAlgorithmName: SHA1 

Even though MyCert.pfx file is SHA256, the cmdlet -Whatif shows SHA1.

If I use server manager to configure AD-CS and import the .PFX file, it correctly installs using SHA256

Am I missing something? Or is the cmdlet bugged.

Workflow Manager security configuration issues?

I have been trying to install the Workflow Manager on our SharePoint farm. I verified that all services are running (Service Bus message broker, Service Bus Gateway, Windows Frabric Host Service and the Workflow Manager backend) and they do under a farm account that I specified.

However, when trying to access the Worfklow Manager site it returns the following XML:

<?xml version="1.0"?>     <ScopeInfo xmlns="http://schemas.microsoft.com/workflow/2012/xaml/activities" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">     <DefaultWorkflowConfiguration/>     <Description>Root Scope</Description>     <LastModified>2014-06-18T15:56:53.21</LastModified>     <LastRevised>2014-06-18T15:56:53.21</LastRevised>     <Path>/</Path>         <SecurityConfigurations>             <ScopedSecurityConfiguration i:type="WindowsSecurityConfiguration">             <Name>Microsoft.Workflow.Management.Security.WindowsSecurityConfiguration</Name>             <WorkflowAdminGroupName>BUILTIN\Administrators</WorkflowAdminGroupName></ScopedSecurityConfiguration>         </SecurityConfigurations>     <Status>Active</Status>     </ScopeInfo> 

What is the resolution for this? I have been going through Microsoft TechNet’s articles but couldn’t troubleshoot the issue.

Thanks for your support.

Unstable 4 Monitor Daisychain Configuration using Ubuntu 18.04.3 and Nvidia K2200 Card on HP Z840

I am attempting to build a 4-monitor workstation on an HP Z840 with Nvidia K2200 graphics card and using Ubuntu 18.04.3 and was hoping someone may have troubleshooting suggestions.

I installed Ubuntu server, desktop and netboot on this hardware and tried both the Nouveau and nvidia-driver-435 driver. In these different package/driver configurations, all four displays were recognized in the “Displays” program. However, only two or three monitors would show the desktop. The remaining monitors were black, even though I could mouse across all four monitors.

Returning to the workstation after it had been idle, I moved the mouse and all four monitors showed the desktop (prior to this only 2 displays were live). After a reboot, only two monitors showed the desktop. I waited for the workstation to enter idle state again. After moving the mouse, three monitors were live and the fourth no longer appeared in the “Displays” systems setting module. The Xorg.0.log does not show errors.

The 4 monitors are Dell U2415 using display port daisychaining where the first 3 monitors are DP1.2 enabled and the last monitor in this chain is not.

I don’t understand this instability. How can I troubleshoot this?

IPv6 static configuration (Ubuntu 19.04)

I’m trying to implement a network for a project where i need a server, a virtual machine running Ubuntu 19.04, with two static ipv4 and ipv6 addresses (one on each interface on the machine) to connect 2 subnet, but editing my /etc/network/interfaces file doesn’t seem to work.

At the moment my configuration is this:

auto enp0s8 iface enp0s8 inet static     address 192.168.20.10     netmask 255.255.255.0     network 192.168.20.0     broadcast 192.168.20.255     gateway 192.168.20.1  iface enp0s8 inet6 static     address fc00::2:0:0:0:a     netmask 64  auto enp0s9 iface enp0s9 inet static     address 192.168.30.10     netmask 255.255.255.0     network 192.168.30.0     broadcast 192.168.30.255     gateway 192.168.30.1  iface enp0s9 inet6 static     address fc00::3:0:0:0:a     netmask 64 

Using the command ip addr show ipv4 works fine but i can only see one of the 2 static ipv6 addresses (every interface also has its fe80: link-local address). How can i fix this?