Adding T attribute to the ca_cert solved the problem.
Thank you for your help.
Eli
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Adding the T attribute to the ca_cert solved the problem.
Thank you for your help!
Eli
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Mon, Apr 1, 2019 at 5:22 AM Patrick O'Callaghan
wrote:
>
> I'm interested in configuring grub to allow selecting different sets of
> kernel parameters at boot time. I know I can edit the boot command line
> by hand, but this is tedious and error-prone. (An example might be to
> choose between
> On 3 Apr 2019, at 04:39, Vandenburgh, Steve Y
> wrote:
>
> Believe that you may need the "T" trust setting on the CA certificate too:
>
> certutil
> -t trustargs
> Specify the trust attributes to modify in an existing certificate
> or to apply to a certificate when
> On 2 Apr 2019, at 23:46, Mark Reynolds wrote:
>
> Hi Jan,
>
> On 4/2/19 5:11 AM, Jan Tomasek wrote:
>> Hi,
>>
>> I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
>> replicas all on RedHat which I would like to abandon in favor Debian
>> which is my main platform.
>>
On 4/2/19 2:43 PM, CLOSE Dave wrote:
Samuel Sieb wrote:
I just tried it and it worked. I was able to add a static address to
my wifi connection while keeping the dhcp one.
"nm-connection-editor" has to be run from the command line, there is
no icon for it. The Gnome connection editor doesn't
Samuel Sieb wrote:
> I just tried it and it worked. I was able to add a static address to
> my wifi connection while keeping the dhcp one.
> "nm-connection-editor" has to be run from the command line, there is
> no icon for it. The Gnome connection editor doesn't support doing
> this.
Perhaps
On 4/2/19 1:40 PM, CLOSE Dave wrote:
I wrote:
For a primary interface with a static address, I may be able to add
the information as IPADDR2 (etc) in ifcfg-eth0. But how do I do this
if the primary interface gets its address via DHCP?
Samuel Sieb answered:
Install "nm-connection-editor".
I wrote:
> For a primary interface with a static address, I may be able to add
> the information as IPADDR2 (etc) in ifcfg-eth0. But how do I do this
> if the primary interface gets its address via DHCP?
Samuel Sieb answered:
> Install "nm-connection-editor". It gives you a lot more
>
On 4/1/19 6:43 AM, David Dusanic wrote:
ToddAndMargo via users:
Where did you find 30?
You can search for packages and even for the upcoming release and EPEL:
https://apps.fedoraproject.org/packages/
Thank you!
___
users mailing list --
On 4/2/19 12:24 PM, CLOSE Dave wrote:
For a primary interface with a static address, I may be able to add the
information as IPADDR2 (etc) in ifcfg-eth0. But how do I do this if the
primary interface gets its address via DHCP?
Install "nm-connection-editor". It gives you a lot more
On every version of Fedora in the last ten years or so, the basic
network configuration is stored in files under /etc/sysconfig. When the
machine boots or I run "systemctl restart network" (or "service network
restart"), those files determine how the network gets set-up. After
that, I can change
Believe that you may need the "T" trust setting on the CA certificate too:
certutil
-t trustargs
Specify the trust attributes to modify in an existing certificate
or to apply to a certificate when creating it or adding it to a
database. There are three available
Hello,
I am trying to setup a mutual based TLS authenticated 389-DS LDAP server, where
the client and the server will perform certificate based authentication.
This should be test system and not a production system.
I have a Windows CA signed on the LDAP server certificate and the client
Hi Jan,
On 4/2/19 5:11 AM, Jan Tomasek wrote:
Hi,
I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
replicas all on RedHat which I would like to abandon in favor Debian
which is my main platform.
My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
Hi,
I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
replicas all on RedHat which I would like to abandon in favor Debian
which is my main platform.
My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
completely missing 389-admin package [1]. They ship
16 matches
Mail list logo
