Proxy config - Linux

 /etc/apt/apt.conf

Acquire{
HTTP::proxy "http://192.168.179.222:80";
HTTPS::proxy "http://192.168.179.222:80";
FTP::proxy "http://192.168.179.222:80";
}

Linhas a serem adicionadas no arquivo /etc/yum.conf

# The proxy server - proxy server:port number
proxy=http://IP_PROXY:PORTA
# The account details for yum connections
proxy_username=USUARIO
proxy_password=SENHA

Linhas no arquivo .bash_profile:

export http_proxy=http://IP_PROXY:PORTA
export https_proxy=http://USUARIO:SENHA@IP_PROXY:PORTA


sudo vi /etc/wgetrc

https_proxy = http://USUARIO:SENHA@IP_PROXY:PORTA
http_proxy = http://USUARIO:SENHA@IP_PROXY:PORTA
ftp_proxy = http://USUARIO:SENHA@IP_PROXY:PORTA

sudo vi /etc/profile

export http_proxy=USUARIO:SENHA@IP_PROXY:PORTA
export ftp_proxy=USUARIO:SENHA@IP_PROXY:PORTA


/etc/environment

http_proxy="http://USUARIO:SENHA@IP_PROXY:PORTA"
https_proxy="http://USUARIO:SENHA@IP_PROXY:PORTA"
ftp_proxy="http:///USUARIO:SENHA@IP_PROXY:PORTA"
no_proxy=localhost,127.0.0.0/8
export http_proxy https_proxy ftp_proxy no_proxy 
 
 

 

Checkpoint enable ICMP redirects

 

To enable ICMP redirects, configure the global kernel parameter fw_icmp_redirects=1 on the Security Gateway.

    • To change the parameter On-the-fly:
      1. Run the command: # fw ctl set int fw_icmp_redirects 1
      2. Verify the new parameter setting with: # fw ctl get int fw_icmp_redirects
To set the parameter value to survive reboot (see details in sk26202)
  1. Edit the $FWDIR/boot/modules/fwkern.conf file.
  2. Add the line: fw_icmp_redirects=1
  3. Reboot

 

Configure Postfix For Relaying to Office 365


To configure our Postfix server for relaying emails through smtp.example.com, we run

postconf -e 'relayhost = YOURDOAMIN.mail.protection.outlook.com'
postconf -e 'smtp_sasl_auth_enable = yes'
postconf -e 'smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd'
postconf -e 'smtp_sasl_security_options ='


Our username (someuser) and password (howtoforge) for smtp.example.com must be stored in /etc/postfix/sasl_passwd, therefore we do this:

echo "YOURDOAMIN.mail.protection.outlook.com  USERMAIL:PASSWORD" > /etc/postfix/sasl_passwd

/etc/postfix/sasl_passwd must be owned by root, and noone else should have read access to that file, so we do this:

chown root:root /etc/postfix/sasl_passwd
chmod 600 /etc/postfix/sasl_passwd

Now we must convert /etc/postfix/sasl_passwd into a format that Postfix can read:

pico main,cf
setgid_group = postdrop
sendmail_path = /usr/sbin/sendmail

postmap /etc/postfix/sasl_passwd

This will create the file /etc/postfix/sasl_passwd.db.

All that is left to do is restart Postfix:

mkfifo /var/spool/postfix/public/pickup
/etc/init.d/postfix restart

That's it. You can now test by sending emails over your mailserver and having a look at your mail log. You should see that all your emails are now passed on to smtp.example.com (except the ones that have a local recipient). 


Updatable objects appear as 'no longer supported'

  Symptoms In some scenarios, the following validation warning appears on an updatable object: " Object is no longer supported. Enforci...

Mais vistos