Language:
switch to room list switch to menu My folders
Go to page: First ... 16 17 18 19 [20]
[#] Wed Oct 30 2019 17:45:47 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: How to hide alternate authentication buttons on the login page

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

We don't need the authentication selector buttons (internal, openid, google,

yahoo, etc) on the login page since we can only use the internal method.


How can I hide or remove the authentication selection buttons?

If you don't want users to be able to create their own accounts, you can disable self-service user account creation. In that case, not only will the social login buttons disappear, but the "new user" button will disappear as well, and you will only be able to log in when an administrator creates a user account.

[#] Wed Oct 30 2019 18:24:12 EDT from calcmandan @ Uncensored

Subject: Re: What is the current released version

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

Where's the easy install script located? Sorry, I"m relearning everything and i'm on painkillers that make me more stupid than usual.

 



[#] Thu Oct 31 2019 09:53:08 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: What is the current released version

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

[#] Thu Oct 31 2019 12:09:03 EDT from FrostyBison @ Uncensored

Subject: Re: How to hide alternate authentication buttons on the login page

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

 

Wed Oct 30 2019 05:45:47 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: How to hide alternate authentication buttons on the login page
We don't need the authentication selector buttons (internal, openid, google,  yahoo, etc) on the login page since we can only use the internal method.
How can I hide or remove the authentication selection buttons?

If you don't want users to be able to create their own accounts, you can disable self-service user account creation. In that case, not only will the social login buttons disappear, but the "new user" button will disappear as well, and you will only be able to log in when an administrator creates a user account.

Our potential use case is on an isolated network (so no social login) but requires on-the-fly registration. So the disable self-service user account creation knob doesn't meet our needs.

My work around is in the the attached patch.



get_logged_in.diff (text/x-diff, 2717 bytes) [ View | Download ]
[#] Fri Nov 01 2019 06:16:56 EDT from mo @ Uncensored

Subject: Access to rooms_circle of friends ++

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

Hi, i would like to know how to deal with controlling who sees what on a citadel installation, when you have more than one group of people, using the system - say friends on one side, and relations on the other (work/ friends etc...) who you want to only grant access to certain rooms/want to keep apart from each other?

 



[#] Fri Nov 01 2019 16:41:40 EDT from anotherpiuser @ Uncensored

Subject: Attachment corruption some diagnostics

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

A fresh Citadel install.

Base os = 2019-09-26-raspbian-buster-lite

The install went smoothly using the Easy Install.

Apache is not part of raspbian lite and was not installed. The essentials installed were:

build-essential curl g++ gettext shared-mime-info libssl-dev zlib1g-dev

Using the internal citadel web server and firefox to access it.

Some of the time when restarting citadel there are port in use errors thrown up, but so far they have always cleared and the server started successfully. I suspect it is some systemd stupidity.

When sending an attachment from one account to another on the same server I have found repeatably so far that:

For a plain text attachment (one byte per character) the attachment when downloaded using the web interface will be corrupted. This is true both for the received email and also for the attachment when downloaded from the sent folder.

For the corrupted file, the first 51 decimal (32hex) characters will be correct. There will then be corruption of 157decimal characters including the insertion of three extra bytes before another set of 51 decimal correct characters. This pattern then appears to repeat.

However if the received email is downloaded by a POP client then the attachment received by the pop client is uncorrupted and correct. I don't have an IMAP client to hand to check its behaviour.

Hopefully the above may help you hunt the bug.

 



[#] Fri Nov 01 2019 17:13:40 EDT from anotherpiuser @ Uncensored

Subject: Re: Attachment corruption some diagnostics

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

As a follow up having just found an IMAP client and checked with it, that again shows no corruption on the attachment. View or download of the attachment in the sent folder by way of the web interface still shows corruption as described.

It seems like the attachment is stored / available uncorrupted but when downloaded or viewed via the citadel web interface it is corrupt.

Hopefully between the corruption description and it appearing to be only in the web interface you can swat this.

If I  made errors with your system terminology the apologies, hopefully you can still follow my thoughts, and because I forgot the versions are:

running Citadel 927 with WebCit 925, server build 927

 

Fri Nov 01 2019 16:41:40 EDT from anotherpiuser @ Uncensored Subject: Attachment corruption some diagnostics

A fresh Citadel install.

Base os = 2019-09-26-raspbian-buster-lite

The install went smoothly using the Easy Install.

Apache is not part of raspbian lite and was not installed. The essentials installed were:

build-essential curl g++ gettext shared-mime-info libssl-dev zlib1g-dev

Using the internal citadel web server and firefox to access it.

Some of the time when restarting citadel there are port in use errors thrown up, but so far they have always cleared and the server started successfully. I suspect it is some systemd stupidity.

When sending an attachment from one account to another on the same server I have found repeatably so far that:

For a plain text attachment (one byte per character) the attachment when downloaded using the web interface will be corrupted. This is true both for the received email and also for the attachment when downloaded from the sent folder.

For the corrupted file, the first 51 decimal (32hex) characters will be correct. There will then be corruption of 157decimal characters including the insertion of three extra bytes before another set of 51 decimal correct characters. This pattern then appears to repeat.

However if the received email is downloaded by a POP client then the attachment received by the pop client is uncorrupted and correct. I don't have an IMAP client to hand to check its behaviour.

Hopefully the above may help you hunt the bug.

 



 



[#] Sat Nov 02 2019 06:27:07 EDT from anotherpiuser @ Uncensored

Subject: Re: Attachment corruption some diagnostics

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

Having just tried fresh easy installs into both a ubuntu 32 bit virtual box and a ubuntu 64 bit virtual box neither show the same symptoms. Both on a 64bit Intel windows 7 host.

It would appear that the problem is Pi architecture specific.

 



[#] Mon Nov 04 2019 14:15:52 EST from calcmandan @ Uncensored

Subject: Screwed up my install of citadel

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

trying to run an easyinstall with a hosed apt update and it keeps stopping at a certain point. i inadvertently deleted my backup so i'm running a disk utility to undelete that directory. in the meantime, i have the database and config files still available. could i start all over with those files and import everything later?

i'd really like to wipe the drive and install the latest ubuntu server, patch it, and reinstall citadel.



[#] Mon Nov 04 2019 15:42:58 EST from calcmandan @ Uncensored

Subject: Re: Screwed up my install of citadel

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

Here is the apt error. I did attmept to manually install dependencies to work around the apt errors, as you can see.

Reading package lists... Done
Building dependency tree      
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
libical-dev is already the newest version (1.0.1-0ubuntu2).
make is already the newest version (4.1-6).
make set to manually installed.
zlib1g-dev is already the newest version (1:1.2.8.dfsg-2ubuntu4.1).
zlib1g-dev set to manually installed.
libldap2-dev is already the newest version (2.4.45+dfsg-1ubuntu1.4).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 libcurl4-openssl-dev : Depends: libcurl3 (= 7.47.0-1ubuntu2.14) but it is not going to be installed
 libexpat1-dev : Depends: libexpat1 (= 2.1.0-7ubuntu0.16.04.5) but 2.1.0-7ubuntu0.16.04.3 is to be installed
 libgnutls-openssl27 : Depends: libgnutls30 (= 3.4.10-4ubuntu1.3) but 3.5.18-1ubuntu1.1 is to be installed
 libgnutls30 : Depends: libc6 (>= 2.25) but 2.23-0ubuntu9 is to be installed
               Depends: libidn2-0 (>= 0.6) but it is not going to be installed
               Depends: libtasn1-6 (>= 4.12) but 4.7-3ubuntu0.16.04.2 is to be installed
               Depends: libunistring2 (>= 0.9.7) but it is not installable
 libical-dev : Depends: libical1a (= 1.0.1-0ubuntu2) but 1.0-1.3 is to be installed
 libssl-dev : Depends: libssl1.0.0 (= 1.0.2g-1ubuntu4.15) but 1.0.2g-1ubuntu4.8 is to be installed
 plymouth-theme-ubuntu-text : Depends: plymouth (= 0.9.2-3ubuntu13.1) but 0.9.2-3ubuntu13.5 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
 Citadel Easy Install is aborting.
 The last few lines above this message may indicate what went wrong.



[#] Mon Nov 04 2019 15:43:59 EST from calcmandan @ Uncensored

Subject: Re: Screwed up my install of citadel

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

apt-get -f install
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libasn1-8-heimdal libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libkrb5-26-heimdal libroken18-heimdal libwind0-heimdal
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libical1a plymouth-theme-ubuntu-text
The following packages will be REMOVED:
  apt-transport-https curl git golang-openldap-dev iputils-ping libcurl3-gnutls libgnutls-openssl27 libgnutls30 libldap-2.4-2 libldap2-dev liblxc1 librtmp1 libvirt-bin libvirt0 lxc-common lxd ntfs-3g python3-pycurl python3-software-properties qemu-block-extra qemu-kvm
  qemu-system-common qemu-system-x86 qemu-utils software-properties-common testdisk ubuntu-minimal ubuntu-server ubuntu-virt-server
The following packages will be upgraded:
  libical1a plymouth-theme-ubuntu-text
2 upgraded, 0 newly installed, 29 to remove and 268 not upgraded.
7 not fully installed or removed.
Need to get 0 B/174 kB of archives.
After this operation, 87.7 MB disk space will be freed.
Do you want to continue? [Y/n] y
Setting up util-linux (2.27.1-6ubuntu3.8) ...
insserv: warning: script 'K01webcit' missing LSB tags and overrides
insserv: warning: script 'webcit' missing LSB tags and overrides
insserv: There is a loop between service webcit and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service plymouth if started
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service unattended-upgrade-shutdown-check at depth 1
insserv: There is a loop at service webcit if started
insserv: There is a loop between service webcit and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service plymouth and udev if started
insserv:  loop involving service mountkernfs at depth 1
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting webcit depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package util-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)



[#] Wed Nov 06 2019 01:21:54 EST from calcmandan @ Uncensored

Subject: Re: Screwed up my install of citadel

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

nevermind i cut my losses and installed fresh OS and new easyinstall.



[#] Wed Nov 06 2019 03:01:50 EST from "brianvind" <brianvind@borgstrom.cc> to <room_citadel_support@citadel.org>

Subject: unsubscribe

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

 



[#] Wed Nov 06 2019 04:04:40 EST from Warlock @ Uncensored

Subject: Limited options for all users

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

Hello,

I want to connect my Citadel Server to my active directory.

The problem is:

All AD users should only see "Notes", "Tasks" and "Log off" and nothing more.

The "customize this menu" button should also be invisible.

What do I have to do?

 

Best regards

Andreas



[#] Sun Nov 10 2019 22:10:53 EST from kdmiller45 @ Uncensored

Subject: config of Citedal

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

I have entered 7 domains in citedal

and have the mx records setup

do I also need to add info in the hostname file in Ubuntu

 

xxx.xxx.xxx.xxx  domainname.com   domainname

 

hope this is the right place for this

 

Keith



[#] Mon Nov 11 2019 03:22:46 EST from "brianvind" <brianvind@borgstrom.cc> to "'Citadel Support'" <room_Citadel_Support@citadel.org>

Subject: RE: [Citadel Support]

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

Hi

How do I unsubscribe from this list?

Brian

-----Original Message-----
From: Citadel Support <room_Citadel_Support@citadel.org>
Sent: 11. november 2019 04:12
To: room_Citadel_Support@citadel.org
Subject: [Citadel Support]

------------------------------------------------------------------------------
From: kdmiller45 <kdmiller45@uncensored.citadel.org>
Subject: config of Citedal

I have entered 7 domains in citedal

and have the mx records setup

do I also need to add info in the hostname file in Ubuntu

Â

xxx.xxx.xxx.xxx domainname.com  domainname

Â

hope this is the right place for this

Â

Keith
------------------------------------------------------------------------------
You are subscribed to the 'Citadel Support' list.
To post to the list: room_citadel_support@citadel.org

[#] Mon Nov 11 2019 04:26:18 EST from mo @ Uncensored

Subject: Re: Access to rooms_circle of friends ++

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

 

Fri Nov 01 2019 06:16:56 EDT from mo @ Uncensored Subject: Access to rooms_circle of friends ++

Hi, i would like to know how to deal with controlling who sees what on a citadel installation, when you have more than one group of people, using the system - say friends on one side, and relations on the other (work/ friends etc...) who you want to only grant access to certain rooms/want to keep apart from each other?

 



I hope i wasn't asking a silly question here. I know rooms can be private/hidden, public or invitation only. I was wondering, without having a working citadel installation for reference,  how to deal with  ' Group Access ' - and keep two groups of people seperate on the same system.

(one system, two use cases)

 

Kind Regards Mike



[#] Tue Nov 12 2019 10:31:04 EST from "s3cr3to" <s3cr3to@uncensored.citadel.org> to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: [Citadel Support]

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

Go there and write **the email address that you used** to subscribe.

https://uncensored.citadel.org/listsub

Regards

On 11/11/19 1:22 AM, brianvind wrote:

Hi

How do I unsubscribe from this list?

Brian

-----Original Message-----
From: Citadel Support <room_Citadel_Support@citadel.org>
Sent: 11. november 2019 04:12
To: room_Citadel_Support@citadel.org
Subject: [Citadel Support]

[#] Tue Nov 12 2019 16:01:44 EST from vorp7 @ Uncensored

Subject: hanging on easy install?

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

Hello and thanks to anyone for any direction/help they can provide -

I'm installing in a Kubuntu virtual machine for testing/demo purposes. I have installed pre-requisites but wehter I wget or curl and use the easyinstall script, the console seems to hang with no errors. There's no indication of any progress, ie. no % total or received displayed under those headings. 

The internet connection is fine and there are no firewall rules that would be stopping something like this - on which end is the problem?



[#] Tue Nov 12 2019 16:35:03 EST from vorp7 @ Uncensored

Subject: Re: hanging on easy install?

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

Replying to my own message to update:

Not sure why it didn't pipe to sh, but I just curl'd it and pasted it into a file, then chmod+x'd it, then ran as su and it's installing. <shrug>



Go to page: First ... 16 17 18 19 [20]