between the seconds of my life

There is a major zero day bug announced in solaris 10 and 11 with the telnet and login combination. It has been verified.  The issue: The telnet daemon passes switches directly to the login process which looks for a switch that allows root to login to any account without a password. If your telnet daemon is running as root it allows unauthenticated remote logins. Telnet should be disabled. Since 1994 the cert.org team has recommended using something other then plain text authentication due to potential network monitoring attacks. http://www.cert.org/advisories/CA-1994-01.html “We recognize that the only effective long-term solution to prevent these attacks is by not transmitting reusable clear-text passwords on the network.“ If remote shell access is required ssh is a better choice then telnet. We have done articles about securing ssh in the past. http://isc.sans.org/diary.html?storyid=1541 The FIX: To disable telnet in solaris 10 or 11 this command should work. svcadm disable tel...

Beberapa kali lewat di padjajaran Bogor, sepertinya ada penampakan "Soto Banjar". Kebetulan adikku yang mau menikah, menanyakan dimana soto banjar yang enak supaya bisa di jadikan salah satu jajanan nanti di resepsi. Dengan berbekal alasan utama "membantu adik" serta verifikasi apakah benar "penampakan" tersebut memang soto banjar. Mumpung liburan, ajak keluarga untuk mencoba makanan tersebut. - "penampakan" soto banjar - Jl. Raya Padjajaran Bogor Kesan pertama sampai disana, ternyata ada namanya "Soto Banjar Bumi Khatulistiwa Bogor" tetapi aduhh parkirnya sudah banget. Paling bisa 3 mobil dan sisanya ya di pinggir jalan atau di ruko yang agak jauh dari sini. Duh kepalang deh sudah sampai, niat harus terlaksanakan. Menu yang terlihat ada soto banjar dan katupat kandangan, tanpa pikir panjang ya pesan dua-duanya saja dan semua "wadai" yang terlihat mata. Memang sudah lama sekali tidak merasakan makanan ini. Katupat ka...

When network service like telnet connection hangs, then it is possible the inetd subsystem is not working properly. # refresh -s inetd 0513-095 The request for subsystem refresh was completed successfully. If the refresh hangs for some time and comes back with 0513-056 time out waiting for command response, then the inetd subsystem may not be working correctly and should then be killed nicely. Run #ps -ef | grep inetd and do a kill -15 on the process ID on the line that has /usr/sbin/inetd. Once inetd has been killed, type startsrc -s inetd. If inetd starts, try to telnet into the machine. If inetd does not start up successfully, or if telnet still hangs indefinitely, run kill -15 on the PID of inetd again. Back up the original /etc/inetd.conf file to a new file name by typing: # mv /etc/inetd.conf /etc/inetd.conf.backup The original template is in /usr/lpp/bos.net/inst_root/etc/. You can copy it by typing: # cp /usr/lpp/bos.net/inst_root/etc/inetd.conf /etc/inetd.conf Run start...