I have an original sendmail.pem that was generated with /etc/pki/tls/certs/make-dummy-cert (which is similar to /etc/pki/tls/certs/Makefile), but it's now expired.
I tried to use the script below to extract the key, subject, and serial #, and generate a new cert based on the same, but for whatever reason Thunderbird balks at it with:
Oct 27 16:59:26 mail sendmail: STARTTLS=server, error: accept failed=0, SSL_error=1, errno=0, retry=-1, relay=macbook.redfish-solutions.com [192.168.1.17]
Oct 27 16:59:26 mail sendmail: STARTTLS=server: 6025:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1195:SSL alert number 42
Oct 27 16:59:26 mail sendmail: q9RMxQX8006025: macbook.redfish-solutions.com [192.168.1.17] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSA
What am I missing? And should that makefile have a:
dummy target that updates a cert? Or do we need a update-dummy-cert script additionally?
Here's the script that I used to update the cert.
I have been running my laptop on various versions of FC without a
problem and am currently on FC16 running Gnome 3 in full mode.
Recently the FC16 Kernel was updated from 3.4.11 to 3.6.2 and my laptop
(Dell Latitude D610 ) would no longer boot - although I could go back to
any 3.4 kernel and it booted ok and worked under Gnome 3. There were no
messages on the failed 3.6.x boot - the screen just went blank. After a
bit of delving it seemed that a similar problem had been reported in
relation to Plymouth and modesetting. Following that track lead me to
'Bug 845745 - kernel version 3.5.0-2 hangs at boot with modesetting:
"conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic
driver" ' on Fedora Bugzilla.
I did try the 'nomodeset', and that does allow a boot under 3.6.2, but
then Gnome 3 goes into fallback mode.
Does anyone know if this will be fixed under FC16, or is this a generic
Kernel fix that will appear across all releases that use that kernel?
How can be used EBTABLES in addition to IPTABLES to forward traffic
from an internal LAN to an external?
Suppose that I have an internal LAN with private IPs, and a Gateway
that control the traffic to the outside, and I only need forward traffic
for certain MAC address regardless IP address.
INTERNET --> Gateway <--- LAN
I'm not sure if I have to enable the following modules in `sysctl.conf`:
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
I have tried with the following configuration, but nothing happens:
# ebtables -F
# ebtables -t nat -F
# ebtables -P INPUT ACCEPT
# ebtables -P OUTPUT ACCEPT
# ebtables -P FORWARD ACCEPT
# ebtables -A FORWARD -i eth0 -o eth1 -j ACCEPT
# ebtables -t nat -A POSTROUTING -s INTERNAL_LAN_CLIENT_MAC -o eth1 \
-j snat --to-source MAC_OF_EXTERNAL_GATEWAY_INTERFACE
Any thought will be highly appreciated.
Thanks in advance,
* Este mensaje de correo electrónico ha sido procesado por el *
* Servidor de Correo Electrónico de Frioclima y es un correo *
* válido para el dominio: frioclima.com.cu *
why is html/css display on fedora on firefox and google chrome alike is
different than on other os ? some times the size of a font can break the
display of a site which looks right on windows and not on fedora.
is there a way to work around this issue by tweaking some settings on
firefox and google chrome ?
I see usb_modeswitch frequently crashing with a segfault, and a message
Oct 31 19:38:28 localhost kernel: [ 33.953670] usb_modeswitch_:
segfault at 7fffd64bfbe4 ip 0000003000874b06 sp 00007fffd64bfbd0 error 6 in
Is there any way to trace back 7fffd64bfbe4 to the function name / line
Thank you in advance, Clemens
I have 1Gb of memory upgrade, so I have enough memory. My SSD is only
4Gb, but I have a 16GB SD card.
So the SSD is setup for /boot with 300Mb, swap with 1.6Gb and the rest
is /var. The SD is /
The challenge with the install is the small screen size. I complained
about this and submitted a bug on it with f14 (which was the only
install I have made on this ee701). Apparently the developers did not
feel it necessary to do anything about adjusting the dialog sizes to the
actual screen size. For the most part I was able to guess what keys to
hit for the buttons cut off below the bottom of the screen. I could not
see how to setup a LVM on the SD, so it is just and ext4 partition.
Also I could not go into customizing the packages for the install and
although I did provide my local repos so I grabbed all the updates right
off, I had to just go with the standard graphic desktop package install....
Next I will have to do the gnome 3 customizations. Though I MIGHT just
leave it for the defaults for a while, rather than all the customzations
I did for this f16 notebook a year ago. I actually would like to wait
for f18 for upgrading my main notebook; I kind of like skipping releases...
Anyway. so far so good.
by Singapore Citizen Mr. Teo En Ming (Zhang Enming)
I need help. I have just installed Fedora 17 from the DVD. I used text
mode installation and later converted to GUI mode using
yum groupinstall "X Window System" Desktop
and configuring systemd.
Please refer to the image below. The GUI cannot display English
characters. All I get are square boxes.
Thank you very much.
Mr. Teo En Ming (Zhang Enming)
My system already had one serial port, ttyS0 which is working.
I've installed a Dynamode 2-port serial card and the kernel sees the two
ports. This provides two ports is:
PCI Spec Revision 2 compliant
Compatible with 16C550 UART
and says that it supports Linux.
However, I can't use them. I've tried using both minicom and faxxaddmodem (I'm
setting up a Hylafax modem bank).
Can anyone suggest what I need to do please.
[root@stan2 ~]# dmesg|grep tty
[ 0.000000] console [tty0] enabled
[ 0.690683] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.711711] 00:04: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.712208] 0000:00:09.0: ttyS1 at I/O 0xec00 (irq = 17) is a XScale
[ 0.712602] 0000:00:09.0: ttyS2 at I/O 0xe880 (irq = 17) is a XScale
[root@stan2 ~]# lspci|grep -i serial
00:09.0 Serial controller: Device 4348:3253 (rev 10)
[root@stan2 ~]# setserial /dev/ttyS1
/dev/ttyS1, UART: undefined, Port: 0xec00, IRQ: 17
[root@stan2 ~]# ll /dev/ttyS*
crw-------. 1 uucp dialout 4, 64 Oct 31 14:33 /dev/ttyS0
crw-rw----. 1 root dialout 4, 65 Oct 31 14:34 /dev/ttyS1
crw-rw----. 1 root dialout 4, 66 Oct 31 14:34 /dev/ttyS2
crw-rw----. 1 root dialout 4, 67 Oct 31 2012 /dev/ttyS3
Group I.T. Manager
I was installing fresh copy of fedora 17. I used /dev/sda, where the windows 7 exists, as bootloader drive. At the end of the installation of packages, error is coming "There was an error installing the bootloader. The system may not be bootable"