Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 [4] 5 6 7 8 ... Last
[#] Sun Dec 05 2021 19:14:05 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

OK, nevermind. I figured out how to fix the XMPP issue, it was a broken certificate.

I spun up a VM, installed Debian Buster, installed the Easy Install version.

Connected to https://ip address, and got the 'no_overlap' error, which led me to a 'bad'

certificate, and led me to creating a new self-signed certificate. Link from web-cit to new

certificate files and viola, working. Now, for a 'new' issue. How do you link the files to

/citadel-data/keys/citadel.* and the necessary stuff to enable the rest of Citadel?



[#] Sun Dec 05 2021 19:16:03 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

for the previous message, it refers to the Docker container files that you can't get to.

 



[#] Sun Dec 05 2021 20:12:28 EST from fang-castro

[Reply] [ReplyQuoted] [Headers] [Print]

anyone have Citadel 345a documentation?

[#] Mon Dec 06 2021 11:19:52 EST from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

Is that really the version you're running? 345a (which at the time would have been written as 3.45a)? That version would be more than 25 years old and only capable of running a text-mode BBS. If that's really what you've got, I'd love to hear more about it!

[#] Mon Dec 06 2021 13:01:39 EST from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Time traveler perhaps? :)



[#] Mon Dec 06 2021 21:01:53 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

Kinda realized that. So the docker version is broken for secure connections?Unable to link them to the internal location?

 

Sun Dec 05 2021 07:16:03 PM EST from StarbaseSSD Subject: Re: Citadel Docker XMPP client

for the previous message, it refers to the Docker container files that you can't get to.

 



 



[#] Tue Dec 07 2021 09:09:55 EST from IGnatius T Foobar

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

It shouldn't be. citadel-data/keys/* should be linked by both Citadel Server and WebCit. You do have to restart the container after updating the certificate though.

[#] Thu Dec 09 2021 11:49:47 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

Before creating new certificate:

root@bap-test:/usr/local/citadel/keys# ls -la
total 8
drwx------ 2 root root 4096 Dec  9 11:27 .
drwxr-xr-x 6 root root 4096 Dec  9 11:27 ..
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.cer -> /citadel-data/keys/citadel.cer
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.csr -> /citadel-data/keys/citadel.csr
lrwxrwxrwx 1 root root   30 Dec  9 11:27 citadel.key -> /citadel-data/keys/citadel.key

after new key but before restarting citadel docker instance:

openssl genrsa -out citadel.key 2048
openssl req -new -key citadel.key -out citadel.csr
openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer

root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec 9 11:39 .
drwxr-xr-x 6 root root 4096 Dec 9 11:27 ..
-rw-r--r-- 1 root root 1359 Dec 9 11:39 citadel.cer
-rw-r--r-- 1 root root 1147 Dec 9 11:38 citadel.csr
-rw------- 1 root root 1679 Dec 9 11:36 citadel.key

Restart docker container
docker restart citadel
root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec 9 11:39 .
drwxr-xr-x 6 root root 4096 Dec 9 11:41 ..
-rw-r--r-- 1 root root 1359 Dec 9 11:39 citadel.cer
-rw-r--r-- 1 root root 1147 Dec 9 11:38 citadel.csr
-rw------- 1 root root 1679 Dec 9 11:36 citadel.key
stop docker container
chmod 777 citadel.*

root@bap-test:/usr/local/citadel/keys# ls -la
total 20
drwx------ 2 root root 4096 Dec 9 11:39 .
drwxr-xr-x 6 root root 4096 Dec 9 11:43 ..
-rwxrwxrwx 1 root root 1359 Dec 9 11:39 citadel.cer
-rwxrwxrwx 1 root root 1147 Dec 9 11:38 citadel.csr
-rwxrwxrwx 1 root root 1679 Dec 9 11:36 citadel.key

Stop docker container.
delete citadel.key
restart citadel container
root@bap-test:/usr/local/citadel/keys# ls -la
total 16
drwx------ 2 root root 4096 Dec 9 11:44 .
drwxr-xr-x 6 root root 4096 Dec 9 11:44 ..
-rwxrwxrwx 1 root root 1359 Dec 9 11:39 citadel.cer
-rwxrwxrwx 1 root root 1147 Dec 9 11:38 citadel.csr
lrwxrwxrwx 1 root root 30 Dec 9 11:44 citadel.key -> /citadel-data/keys/citadel.key

Key is now linked but back to broken.



[#] Thu Dec 09 2021 13:11:44 EST from StarbaseSSD

Subject: Re: Citadel Docker XMPP client

[Reply] [ReplyQuoted] [Headers] [Print]

Found a work-around / fix.

=====

sudo apt install docker.io -y
sudo usermod -aG docker pi
sudo mkdir /citadel-data
reboot
docker run -d --restart=unless-stopped --network host \
--volume=/citadel-data:/citadel-data \
--name=citadel citadeldotorg/citadel

docker stop citadel

sudo cd /citadel-data/keys
sudo rm -f citadel.*
sudo openssl genrsa -out citadel.key 2048
sudo openssl req -new -key citadel.key -out citadel.csr
     Answer the questions to the best of your ability
sudo openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer
sudo chmod 777 citadel.*
docker start citadel
Connect to Citadel:
https://<ip_address>
username: admin
password: citadel

You get the warning about a self-signed certificate, and you can accept the exception
now, and all the ssl functionality now works in the other connections with the same limitation.

Feel free to use it, update docs, fix the issue for real.



[#] Thu Dec 09 2021 22:05:26 EST from paulb

Subject: Re: Mail attachments

[Reply] [ReplyQuoted] [Headers] [Print]

I've tried increasing the maximum message length to 40485760, still wont load a image attached, file size is 43.6 kB (43,551 bytes). It shows up, just has a broken image icon and doesn't load the attachment still. I cant figure it out.

Sat Dec 04 2021 15:06:19 EST from s3cr3to Subject: Re: Mail attachments
Try increasing the message limit (20 -> 25mb).
Attachments increase in size when encoded to base64; I think they increase by 20 to 40% of their original size or less but...

From my own experience, if the attachment makes it to the mailbox but the limit is insufficient to contain it, the attachment will arrive corrupted.

On 12/3/21 15:14, paulb wrote:

Hello,

Fair enough, sorry haha.

Its running on raspbian, build 939.

I've tried several attachments, images, a mp3, pdf files, text files. All of them are under the maximum message limit (I have set to 20 mb i believe).

The email shows up fine, it shows there's an attachment, and it has the file-size correct. When you go to view or download it, the file contains no data.

I'm assuming its not downloading the attachment with the message for some reason?

 

Thanks for your fast reply.

 

Fri Dec 03 2021 17:02:04 EST from IGnatius T Foobar Subject: Re: Mail attachments
Well, you could start by providing enough details for us to help you troubleshoot.
Citadel version, operating system and hardware architecture, what type and size attachments you are trying to deal with, whether you are trying to open them in WebCit or a client software, etc. Don't make us play 20 Questions.

 




 



[#] Fri Dec 10 2021 16:15:44 EST from paulb

Subject: Mail attachments

[Reply] [ReplyQuoted] [Headers] [Print]

Mail attachments wont receive correctly. I managed to send a text document attached, but ended up with text like the following; 

ensure that when the wor����2F��R��R�fR6��f�FV�6P��F�R&�6W72�B�W"��O�egrity.

 

There was no formatting in the original document.

I'm assuming this is why no other files are working correctly, the information is corrupted.

Citadel 939 with WebCit 939, server build 939



[#] Sat Dec 11 2021 16:15:21 EST from meshmark

Subject: User Time Zone

[Reply] [ReplyQuoted] [Headers] [Print]

How does one set their user time zone? I've gone to my Preferences and settings page and am able to change my time format. But, nowhere on that page is an entry for setting for my time zone.

Reason I ask, I have just been admitted to a Citadel machine in Oregon (as an admin) and I live in New Jersey. In particular, getting a calendar entry correct seems difficult. Indeed, under Administration -> General site configuration items there is something called "Default timezone for unzoned calendar items". This would seem to indicate that Citadel is looking for someone's time zone when he makes a calendar entry.  Thus, my question.

Regards

 



[#] Sat Dec 11 2021 16:24:33 EST from meshmark

Subject: Re: User Time Zone

[Reply] [ReplyQuoted] [Headers] [Print]

Further info:

The system in question has the "Default timezone for unzoned calendar items" set to "America/Los Angeles". This appears to be set correctly for where the machine is located. Unfortunately, when I access the calendar, the dates/times appear to be in UTC. Something seems to be missing...

 



[#] Tue Dec 14 2021 09:10:17 EST from whitejack

[Reply] [ReplyQuoted] [Headers] [Print]

Why is citadel not packed for Debian 11?

 



[#] Tue Dec 14 2021 14:14:32 EST from s3cr3to to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: (no subject)

[Reply] [ReplyQuoted] [Headers] [Print]

Although for ease I would ask the same question some time ago.

Today I can say that Citadel presents several options that could be better than a debian package:

From https://www.citadel.org/download.html
A script for installation (EasyInstall) and a Docker version, and even the source code.

The latter needs an enthusiastic volunteer to create and maintain the package for Debian. (note the emphasis)


Personally, I am currently struggling trying to understand Docker (especially in allocating the space I need to migrate).
And of course, I have no doubt that once I master this it will be very easy (... ¿easy? ).

On 12/14/21 07:10, whitejack wrote:

Why is citadel not packed for Debian 11?

 




[#] Tue Dec 14 2021 17:02:10 EST from StarbaseSSD

Subject: Re: Docker container of Citadel is now ready to download

[Reply] [ReplyQuoted] [Headers] [Print]

Peter:

Found a work-around / fix for keys in the docker container. I have tested in both a RaspberryOS host, and a Debian 11 host, YMMV.

Note: The shared volume I had to change from /usr/local/citadel to /citadel-data to get it to work.

=====

sudo apt install docker.io -y
sudo usermod -aG docker pi
sudo mkdir /citadel-data
reboot
docker run -d --restart=unless-stopped --network host \
--volume=/citadel-data:/citadel-data \
--name=citadel citadeldotorg/citadel

docker stop citadel

sudo cd /citadel-data/keys
sudo rm -f citadel.*
sudo openssl genrsa -out citadel.key 2048
sudo openssl req -new -key citadel.key -out citadel.csr
     Answer the questions to the best of your ability
sudo openssl x509 -req -days 365 -in citadel.csr -signkey citadel.key -out citadel.cer
sudo chmod 777 citadel.*
docker start citadel
Connect to Citadel:
https://<ip_address>
username: admin
password: citadel

You get the warning about a self-signed certificate, and you can accept the exception
now, and all the ssl functionality now works in the other connections with the same limitation.

Feel free to use it, update docs, fix the issue for real.



[#] Wed Dec 15 2021 05:52:34 EST from sciens

[Reply] [ReplyQuoted] [Headers] [Print]

I just saw your request for a gdb trace.

 

I have not done this before. But I enabled the debuginfo repo and installed the requested packages while trying to run a debug. Let me know if this is correct....

 

[root@mailsrv01 ~]# gdb /usr/local/citadel/citserver
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-16.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/citadel/citserver...done.
(gdb) start
Temporary breakpoint 1 at 0x4179aa: file server_main.c, line 73.
Starting program: /usr/local/citadel/citserver
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe2f8) at server_main.c:73
73      server_main.c: No such file or directory.
(gdb)



[#] Wed Dec 15 2021 08:37:14 EST from sciens

[Reply] [ReplyQuoted] [Headers] [Print]

I just saw your request for a gdb trace.

 

I have not done this before. But I enabled the debuginfo repo and installed the requested packages while trying to run a debug. Let me know if this is correct....

 

[root@mailsrv01 ~]# gdb /usr/local/citadel/citserver
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-16.el8
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/citadel/citserver...done.
(gdb) start
Temporary breakpoint 1 at 0x4179aa: file server_main.c, line 73.
Starting program: /usr/local/citadel/citserver
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffe2f8) at server_main.c:73
73      server_main.c: No such file or directory.
(gdb)



[#] Wed Dec 15 2021 13:59:19 EST from s3cr3to to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Docker version, reporting some bugs with aliases

[Reply] [ReplyQuoted] [Headers] [Print]

Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.

But, in order to "see" my vcard I need to perform the following steps:
  • Open "Contacts".
  • Go to: Administration - User account management - Add, change, delete user accounts
    • Search & select for an account (mine for example)
    • Click on "Edit address book entry".
    • Show a window with title "Contacts" only with my name "My Name" + Click on the button "Cancel".
    • Click on the "Cancel" button
    • Displays another window identical to the Contacts window with my name
    (no - (no     
    My Name
  • Click on my name
  • Shows my vcard
  • Click below on "[edit]"
My: Primary Internet e-mail address and Internet e-mail aliases appear.
Here I can edit and add addresses.
Issue 2: My primary address shows incorrect; it always shows something different if I change it and go back to edit vcard
  • Save changes (if I correct or add something)
  • The "Basic commands" window is displayed
Issue 3:
Although the vcard displayed shows a number of aliases.
When editing, it removes one address at random from the list of aliases.
If I save without adding, is deletes the missing address.
Every time I repeat the process, it changes the primary and when editing it removes a random address.
And so on ad-nauseum.

Regards


[#] Thu Dec 16 2021 14:26:51 EST from Art Cancro to s3cr3to <s3cr3to@uncensored.citadel.org>, Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: Docker version, reporting some bugs with aliases

[Reply] [ReplyQuoted] [Headers] [Print]

To edit the email aliases for a user:

1. From the main screen, select "Administration"

2. Under the "User account management" menu, select "Add, change, delete user accounts"

3. Select the user to be edited, and click "Edit configuration"
     (do not click "Edit address book entry".  It is not there anymore.)

4. On this screen, "Primary Internet e-mail address" is the address that will be used for all outgoing mail.  The user can also receive mail at this address.

5. "Internet e-mail aliases" is where you would put any additional addresses for the user, separated by commas.  The user can receive mail at any of these addresses.


You can also edit a user's email addresses in the text mode client, using the .Aide User-edit command.


Again, there is no longer any ability to edit email addresses from the user's address book entry.  That was a hack that has been removed.



On 12/15/21 13:59, s3cr3to wrote:
Good day
I have some issues with the docker version unning Citadel 941 with WebCit 941, server build 941

Issue 1. I cannot find a shortcut to edit my address and aliases.



Go to page: 1 2 3 [4] 5 6 7 8 ... Last