Jump to content

bunnadik

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by bunnadik

  1. (This is sort of a "Bump")

     

    From what I can tell the problem is that XDMCP doesn't work with XKB (at least not in my setup).

    When I run X locally (through startx or g/k/xdm) it reads /etc/X11/xorg.conf to find 'Option XkbLayout" "fi" ' but when I access X through XDMCP the displaying PC has no knowledge about this.

     

    Is there some way to make XDMCP read and export the server's (well it's technically the client since X has the reversed server-client model) xkb info?

     

    - Peder

  2. Are you sure?

    I've had this server up and running since end of March with name based SSL virtual hosts.

    I tested this on another MDK-10.1 server:

    NameVirtualHost *:443
    <VirtualHost *:443>
    ServerName www2.myserver.org
    DocumentRoot /var/www/html/ssl
    ServerAdmin root@myserver.org
    ErrorLog logs/ssl_error_www2_log
    <IfModule mod_log_config.c>
    TransferLog logs/ssl_access_www2_log
    </IfModule>
    SSLEngine on
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
    SSLCertificateFile /etc/ssl/apache2/server.crt
    SSLCertificateKeyFile /etc/ssl/apache2/server.key
    CustomLog logs/ssl_request_log \
             "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
    
    RewriteEngine On
    RewriteOptions inherit
    </VirtualHost>

    This worked flawlessly.

    I don't know why the apache docs claim "Name-based virtual hosting cannot be used with SSL secure servers". Further down they say "If you're planning to use multiple ports (e.g. running SSL) you should add a Port to the argument, such as *:80" indicating (to me) that SSL does work in name-based hosting.

     

    The only thing I did recently is to install the latest security fixes from Mandriva but I can't see anything there that should affect apache/openssl.

     

    - Peder

  3. I shut down apache (along with most other services) to run chkrootkit and avoid false positives

    regarding hidden processes. When I restarted apache it wouldn't start, complaining about

    [emerg] (13)Permission denied: couldn't grab the accept mutex

     

    After a couple of restarts I saw it complaining about dead semaphores so I used ipcrm to remove

    them, and I even rebooted eventually, but still the same errors. I found that if I start apache

    without SSL it works.

     

     

    I'm running MDK 10.1 with these:

    apache-conf-2.0.50-4mdk

    apache2-mod_php-2.0.50_4.3.8-2mdk

    apache2-mod_perl-2.0.50_1.99_16-1mdk

    apache2-manual-2.0.50-7.2.101mdk

    apache2-mod_proxy-2.0.50-7.2.101mdk

    apache2-modules-2.0.50-7.2.101mdk

    apache2-mod_disk_cache-2.0.50-7.2.101mdk

    apache2-mod_suexec-2.0.50-3mdk

    apache2-mod_ssl-2.0.50-4.1.101mdk

    apache2-2.0.50-7.2.101mdk

    apache2-common-2.0.50-7.2.101mdk

    apache2-mod_cache-2.0.50-7.2.101mdk

     

    I have a couple of virtual hosts, some of them requiring SSL.

     

    - Peder

  4. When i do a telnet on my server, I don't see any of these lines:

    S: 250-AUTH PLAIN LOGIN DIGEST-MD5 CRAM-MD5 GSSAPI

    S: 250-AUTH=PLAIN LOGIN DIGEST-MD5 CRAM-MD5 GSSAPI

    You need to install the plugins :

    urpmi libsasl2-plug-plain
    urpmi libsasl2-plug-crammd5
    urpmi libsasl2-plug-digestmd5
    urpmi libsasl2-plug-gssapi

    Note that I still haven't got it working though.

     

    - Peder

  5. well it was pretty cool that mandrake (10.0) still runs after upgrading cpu and motherboard, the only problem i have now is, that it wont start eth0 at boot time.

    (boot message : bringing up eth0 ... [failed])

     

    My guess is that your new MB has another NIC than the old.

    When you've got ti working by "Add new connection..." do a 'lsmod' as root and see which

    NIC module is loaded (let pretend it's via-rhine). Then 'echo via-rhine >> /etc/modprobe.preload'

     

    - Peder

×
×
  • Create New...