1 d1f529f4 2005-10-29 devnull upas:
 2 d1f529f4 2005-10-29 devnull 	from thread(3):
 3 d1f529f4 2005-10-29 devnull 		It is not safe to call rfork in a  threaded  program,  except  to  call
 4 d1f529f4 2005-10-29 devnull 		rfork(RFNOTEG) from the main proc before any other procs have been cre-
 5 d1f529f4 2005-10-29 devnull 		ated.  To create new processes, use proccreate.
 6 d1f529f4 2005-10-29 devnull 
 7 d1f529f4 2005-10-29 devnull 
 8 d1f529f4 2005-10-29 devnull upas/fs:
 9 d1f529f4 2005-10-29 devnull 	when serving a file writes tbox.tmp when writing back tbox.
10 d1f529f4 2005-10-29 devnull 	make L.mbox in home directory (sometimes)
11 d1f529f4 2005-10-29 devnull 
12 d1f529f4 2005-10-29 devnull 	=======> auth stuff:
13 d1f529f4 2005-10-29 devnull 	Server, Certificate, ...
14 d1f529f4 2005-10-29 devnull 	
15 d1f529f4 2005-10-29 devnull 	    * POP3/IMAP Server (receiving emails): mail.physik.fu-berlin.de (unchanged)
16 d1f529f4 2005-10-29 devnull 	    * SMTP Server (sending emails): mail.physik.fu-berlin.de (unchanged and not relevant for this change [no STARTTLS/SMTP_AUTH])
17 d1f529f4 2005-10-29 devnull 	    * Certificate Authority (CA) Certificate: cacert.crt (CN=ZEDV)
18 d1f529f4 2005-10-29 devnull 	      SHA1 Fingerprint: 37:19:00:47:BB:91:20:94:3B:AA:A7:75:57:D5:4C:0D:EA:5C:18:D9
19 d1f529f4 2005-10-29 devnull 	      MD5 Fingerprint: 56:58:1C:91:DC:08:1B:42:D0:C2:D6:D4:FF:28:AE:C5
20 d1f529f4 2005-10-29 devnull 	    * mail.physik.fu-berlin.de Fingerprints (IMAP/POP3):
21 d1f529f4 2005-10-29 devnull 	      SHA1 Fingerprint: 75:C6:A5:1E:CB:F4:33:2E:95:85:A0:65:87:71:19:08:3D:19:FE:7D
22 d1f529f4 2005-10-29 devnull 	      MD5 Fingerprint: 67:76:23:98:65:0A:39:44:5B:79:BD:91:31:49:59:7A
23 d1f529f4 2005-10-29 devnull 	
24 d1f529f4 2005-10-29 devnull 	The fingerprints can be displayed in the mail clients and can be optained using:
25 d1f529f4 2005-10-29 devnull 	
26 d1f529f4 2005-10-29 devnull 	openssl s_client -connect mail.physik.fu-berlin.de:993 -showcerts # IMAP
27 d1f529f4 2005-10-29 devnull 	openssl s_client -connect mail.physik.fu-berlin.de:995 -showcerts # POP3
28 d1f529f4 2005-10-29 devnull 	
29 d1f529f4 2005-10-29 devnull 	Save all between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----
30 d1f529f4 2005-10-29 devnull 	
31 d1f529f4 2005-10-29 devnull 	openssl x509       -noout -fingerprint -in mail.physik.fu-berlin.de.pem # MD5
32 d1f529f4 2005-10-29 devnull 	openssl x509 -sha1 -noout -fingerprint -in mail.physik.fu-berlin.de.pem # SHA1
33 d1f529f4 2005-10-29 devnull 	
34 d1f529f4 2005-10-29 devnull 	<======= auth stuff
35 d1f529f4 2005-10-29 devnull 
36 d1f529f4 2005-10-29 devnull upas/ned:
37 d1f529f4 2005-10-29 devnull 	need to understand singleton stuff.
38 d1f529f4 2005-10-29 devnull 	
39 d1f529f4 2005-10-29 devnull 	need to understand wait (cf lpdaemon.c ~315)  is it safe to fork in a threaded prog? shoud i use proccreate?
40 d1f529f4 2005-10-29 devnull 	
41 d1f529f4 2005-10-29 devnull 	routines to check/fix:
42 d1f529f4 2005-10-29 devnull 		appendtofile()
43 d1f529f4 2005-10-29 devnull 		switchmb()
44 d1f529f4 2005-10-29 devnull 		rooted()
45 d1f529f4 2005-10-29 devnull 		plumb() <= understand how this works, it may help in deciding how to present attachments in acme/Mail
46 d1f529f4 2005-10-29 devnull 	
47 d1f529f4 2005-10-29 devnull 
48 d1f529f4 2005-10-29 devnull upas/marshal:
49 d1f529f4 2005-10-29 devnull 	some attachments work, some don't. looks like pdf files work while ps don't!? problem in body64()
50 d1f529f4 2005-10-29 devnull 	actually, it seems like the size of attachment is the problem: large attacments don't seem to work, somewhere between 19967 and 161065 is the failure point.