| 1 |
<h3>jonen's notes - 2003-02</h3> |
| 2 |
<hr/> |
| 3 |
|
| 4 |
- Unix-Systems |
| 5 |
o learn howto move/maintain /etc of servers at cvs !! |
| 6 |
Debian: |
| 7 |
x search if new packages available, do 'apt-get --dry-run upgrade'! |
| 8 |
x build small systool script 'apt-get_remote.pl' which do a cronly 'apt-get --dry-run upgrade' and send output via mail |
| 9 |
o review 'apt-get_remote.pl' |
| 10 |
o what's about parsing some response for comand like installing some marked packages |
| 11 |
FreeBSD(stable): |
| 12 |
o read more about BSD package systems (pkg, cvsup) |
| 13 |
x for simple package installation/de-installation use pkg |
| 14 |
x install downloaded package: |
| 15 |
:# pkg_add {package}-{version}.tgz |
| 16 |
x install package via remote server(only if package is available as *latest*): |
| 17 |
pkg_add -r {package}.tgz |
| 18 |
x using cvsup |
| 19 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html |
| 20 |
x newbies could use cvsupit: |
| 21 |
:# pkg_add -r cvsupit.tgz |
| 22 |
- cvsupit will proberly ask you for the default values it |
| 23 |
place at /etc/cvsupfile, which is used by cvsup |
| 24 |
- after that it will start cvsup to update your system |
| 25 |
x if /etc/cvsupfile already exists and you know what you do, |
| 26 |
this command will update your system (maybe run it via cron...): |
| 27 |
:# /usr/local/bin/cvsup -g -L 2 /etc/cvsupfile |
| 28 |
where '-g' tells cvsup not to use a GUI, '-L 2' sets default output level to 2 |
| 29 |
x for available cvs tags, look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html |
| 30 |
o whats about daemon start-stop scripts (like at linux: /etc/init.d/) ? |
| 31 |
x configure and compile custom kernel: |
| 32 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html |
| 33 |
x create custom kernel conf-file |
| 34 |
- cd usr/src/sys/i386/conf/ |
| 35 |
- copy default kenrnel GENERIC to eg MYKERNEL |
| 36 |
- edit/modify MYKERNEL |
| 37 |
x configure sources(really?) |
| 38 |
- run /usr/sbin/config MYKERNEL |
| 39 |
x build kernel |
| 40 |
- cd ../../MYKERNEL |
| 41 |
- make depend |
| 42 |
- make |
| 43 |
- make install |
| 44 |
x use packet fiters (firewall): |
| 45 |
x read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html |
| 46 |
x some options at the kernel have to be enabled: |
| 47 |
- options IPFIREWALL |
| 48 |
Compiles into the kernel the code for packet filtering. |
| 49 |
- options IPFIREWALL_VERBOSE |
| 50 |
Enables code to allow logging of packets through syslogd. |
| 51 |
Without this option, even if you specify that packets should be logged in the filter rules, |
| 52 |
nothing will happen. |
| 53 |
- options IPFIREWALL_VERBOSE_LIMIT=10 |
| 54 |
Limits the number of packets logged through syslogd on a per entry basis. |
| 55 |
You may wish to use this option in hostile environments in which you want to log firewall activity, |
| 56 |
but do not want to be open to a denial of service attack via syslog flooding. |
| 57 |
When a chain entry reaches the packet limit specified, logging is turned off for that particular entry. |
| 58 |
To resume logging, you will need to reset the associated counter using the ipfw(8) utility: |
| 59 |
:# ipfw zero 4500 |
| 60 |
Where 4500 is the chain entry you wish to continue logging. |
| 61 |
- options IPFIREWALL_DEFAULT_TO_ACCEPT |
| 62 |
This changes the default rule action from ``deny'' to ``allow''. |
| 63 |
This avoids the possibility of locking yourself out if you happen to boot a kernel with IPFIREWALL support but have not configured your firewall yet. |
| 64 |
It is also very useful if you often use ipfw(8) as a filter for specific problems as they arise. |
| 65 |
Use with care though, as this opens up the firewall and changes the way it works. |
| 66 |
x firewall is enabled at /etc/rc.conf (or /etc/rc.conf.local) |
| 67 |
firewall_enabled = "YES" |
| 68 |
firewall_type = "{firewall_type}" |
| 69 |
x where {firewall_type} is either a case at /etc/rc.firewall (/etc/rc.firewall6 for ipv6) |
| 70 |
or some custom file to read rules from. |
| 71 |
x Use firewall_type = "OPEN" for default policy 'OPEN' (allow all) |
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
- QoS (Quality of Services) |
| 76 |
o check it out ! |
| 77 |
|
| 78 |
- Apache/php: |
| 79 |
- apache aliases - redirect '/' to index.php (used for url catching/rewriting) |
| 80 |
|
| 81 |
- PHP: |
| 82 |
x search for php widget lib |
| 83 |
x APL (http://apl.sourceforge.net) |
| 84 |
- huge lib in pure C |
| 85 |
x phphtmllib (http://phphtmllib.newsblob.com) |
| 86 |
a mainly widget/render lib, written in php, complete OO-based |
| 87 |
and with nice DataList rendering (abstract source API) |
| 88 |
x integrated with flib |
| 89 |
x wrote some classes to browse data-objects via class DataList (new classes flibRPCDataSource, ObjectList, TsBackend) |
| 90 |
o rename flibRPCDataSource (maybe rework to get more abstract) |
| 91 |
o review ObjectList amd move it to phphhtmllib |
| 92 |
x semi-integraded with class FormBuilder from binarycloud via interface class FormElementsInterface |
| 93 |
x new class DataItem, which render one data object for viewing/editing |
| 94 |
x integrated new FormProcessing classes from phphtmllib (released one day after interface to binaryclouds Formbuilder was written ;) |
| 95 |
x refactored DataItem to use now phphtmllib form processing instead of interface to binarycload |
| 96 |
o review code and move to phphtmllib |
| 97 |
o XOOPS (http://xoops.org) |
| 98 |
XOOPS is a dynamic OO (Object Oriented) based open source portal script written in PHP. |
| 99 |
It is the ideal tool for developing small to large dynamic community websites, intra company portals, |
| 100 |
corporate portals, weblogs and much more. |
| 101 |
o binarycloud (http://binarycloud.com) |
| 102 |
binarycloud is an enterprise class web application platform. binarycloud shares many of the capabilities of products |
| 103 |
like Oracle 9i AS (Application Server) and IBM's WebSphere: |
| 104 |
Proper definition of a framework: "A framework supplies the infrastructure and mechanisms that execute a policy for |
| 105 |
interaction between abstract components with open implementations" |
| 106 |
- benefits: |
| 107 |
x much code done yet! |
| 108 |
- drawbacks: |
| 109 |
o not-really 100% clean code |
| 110 |
o complex app which gives you only limited possibilities to use only some classes, so not very modular |
| 111 |
|
| 112 |
|
| 113 |
- OpenLDAP: |
| 114 |
- Contacts: |
| 115 |
o Evolution: modify/create schema (map Attribute) so the field 'Note' and others can be used |
| 116 |
|
| 117 |
- PAM + SASL |
| 118 |
o seems pam will only works(will only be activated) if plain passwords are used |
| 119 |
o read more about PAM special in co-operate with SASL !! |
| 120 |
|
| 121 |
- Kerberos V |
| 122 |
x use GQ LdapBrowser with SASL to authenticate against ldap |
| 123 |
- this requires a 'kinit <username>' at the shell to get the kerberos ticket |
| 124 |
- ldap will check your ticket pricipial against its acl's ! |
| 125 |
o 'libpam-ldap' from Turbo is bad, don't use it !! (remember at 'apt-get upgrade' !!) |
| 126 |
o write this down in some (existing e.g. sendmail?) howto |
| 127 |
|
| 128 |
- Sendmail |
| 129 |
o research some about sendmail-cluster, 2 mx records, howto to set up second mx/cluster? |
| 130 |
x backup mx: |
| 131 |
- set up second mx at dns |
| 132 |
- add at backup mx place some like this at /etx/mail/mailtertable: |
| 133 |
domain.com esmtp:[123.123.123.123] |
| 134 |
where the ip points to the system the real user accounts |
| 135 |
and add every domain to /etc/mail/relay-domains: |
| 136 |
domain.com |
| 137 |
o whats about these *open* relaying rules(security ?!?) |
| 138 |
x simple load balancing: |
| 139 |
- set up two(or more) mx records with same priority at dns |
| 140 |
- add at every mx place some like this at /etx/mail/mailtertable: |
| 141 |
domain.com esmtp:[123.123.123.123] |
| 142 |
where the ip points to the system the real user accounts are |
| 143 |
note: this will do load balancing between eg 2 mail server, but if one fails, |
| 144 |
there is only a 50% chance that sent messages would arrive |
| 145 |
o change '/etc/init.d/amavisd' to '/etc/init.d/amavis-milter' in howto |
| 146 |
o migrationtools: |
| 147 |
o patch migrationtools for sendmail aliases support (/usr/share/migrationtools/migrate_aliases.pl) |
| 148 |
o create, or search web for, migrationtool for sendmail virtusertable (/usr/share/migrationtools/migrate_virtuser.pl) |
| 149 |
o review patched kerberosV support at /usr/share/migrationtools/migrate_user.pl? |
| 150 |
|
| 151 |
|
| 152 |
- MySQL: |
| 153 |
o move this to mysql-common-tasks howto |
| 154 |
- Create Database |
| 155 |
:# mysqladmin create <database> |
| 156 |
- Set Privileges on databases(creates user too, if not exists...): |
| 157 |
mysql>grant all on {database}.* to {user} identified by "{pass}"; |
| 158 |
mysql>grant all on {database}.* to {user}@{domain} identified by "{pass}"; |
| 159 |
|
| 160 |
|
| 161 |
- Document saving: |
| 162 |
o remember *.doc is a non-standard, bloated Mircosoft format, use HTML instead !! |
| 163 |
see http://www.fsf.org/philosophy/no-word-attachments.html |
| 164 |
|
| 165 |
- my documents: |
| 166 |
o convert all howto's to SDF format ( look at 'nfo/doc/computing/sysadmin/linux/example_sdf_howto.sdf' ) |
| 167 |
o learn more about Lyx/LaTex |
| 168 |
o convert all howto's to LaTex format ( look at 'nfo/doc/computing/sysadmin/linux/example_latex_howto.lyx' ) |
| 169 |
|
| 170 |
|
| 171 |
|
| 172 |
|
| 173 |
future: |
| 174 |
o build 'black box' to trace for 'spys' at a isdn/internet connection ;) |
| 175 |
|
| 176 |
<hr/> |
| 177 |
$Id$ |
| 178 |
|
Parent Directory
| 
Revision Log
