headers
bytemark@bytemarks.net | 3 May 2003 06:06

Re: miniserv.pem

A Thawte or Verasign cert works fine but for CAs using Entrust, GTE, and others for their root, a chained cert
with the root and intermediate certificate(s) is needed or the browser won't recognize the CA as trustworthy.

More details can be found at 

http://www.instantssl.com/support/cert_installation/index.html

It would be nice to see Webmin added to the list of supported  servers along with the likes of Plesk, Hsphere,
Ensim and others. : )

Jamie Cameron <jcameron <at> webmin.com> wrote ..
> I'm surprised that webmin cares at all, because it never tries to 
> validate the server cert. What goes wrong exactly?
> 
>   - Jamie
> 
> bytemark <at> bytemarks.net wrote:
> > The server's own cert.
> > 
> > Thanks,
> > 
> > Rick
> > 
> > Jamie Cameron <jcameron <at> webmin.com> wrote ..
> > 
> >>bytemark <at> bytemarks.net wrote:
> >> > Jamie,
> >> >
> >> > Any plans to allow chained root certificates? InstantSSL and others
> >> > now provide reasonably priced SSL Certs which would be great for
(Continue reading)

Permalink | Reply | 2 comments |
headers
randyf | 16 May 2003 23:40

[webmin-devel] mode 700 directories


  I recently noticed that 5 directories

    time/lang
    time/help
    time/images
    mysql/images
    inittab/help

 Are all mode 700.  Is there a reason this was done, or is it some
artifact?

  Thanks!

	---- Randy

-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
-
Forwarded by the Webmin development list at webmin-devel <at> webmin.com
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-devel
Permalink | Reply | 2 comments |
headers
randyf | 16 May 2003 23:55

Re: [webmin-devel] mode 700 directories


  Hope this doesn't open a can of worms, but as I look more, there seems
to be an odd set of permissions, some 755 others 775, the occasional
744, and a 655 (not to mention the 644/664 differences).  Would it not
make more sense to have a common set of modes (not to mention a suggested
owner:group selection)?

  Thanks again!

	---- Randy

On Fri, 16 May 2003 randyf <at> sibernet.com wrote:

>
>
>   I recently noticed that 5 directories
>
>     time/lang
>     time/help
>     time/images
>     mysql/images
>     inittab/help
>
>  Are all mode 700.  Is there a reason this was done, or is it some
> artifact?
>
>
>   Thanks!
>
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jamie Cameron | 17 May 2003 04:05

Re: [webmin-devel] mode 700 directories

Those directory permissions are definately wrong, as all files in the 
webmin programs dir should be readable by all users (by writable only 
by root). I'll definately fix this in the next release ..

The other permission problems aren't such a big deal, but I guess they 
should be fixed up for consistency's sake as well :)

  - Jamie

randyf <at> sibernet.com wrote:
> 
>   Hope this doesn't open a can of worms, but as I look more, there seems
> to be an odd set of permissions, some 755 others 775, the occasional
> 744, and a 655 (not to mention the 644/664 differences).  Would it not
> make more sense to have a common set of modes (not to mention a suggested
> owner:group selection)?
> 
>   Thanks again!
> 
> 	---- Randy
> 
> On Fri, 16 May 2003 randyf <at> sibernet.com wrote:
> 
> 
>>
>>  I recently noticed that 5 directories
>>
>>    time/lang
>>    time/help
>>    time/images
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Cooper | 18 May 2003 03:55

[webmin-devel] Module RPM naming convention

Hey Jamie and all,

I know I've seen you mention this somewhere before, but I can't recall 
the specifics.

What naming convention is Webmin looking for when installing a module 
from RPM using the Webmin Modules module?  I'm rebuilding all of my 
module RPMs for Red Hat 9, and would like to get it right this time.  ;-)

Thanks!
--

-- 
Joe Cooper <joe <at> swelltech.com>
Web caching appliances and support.
http://www.swelltech.com

-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
-
Forwarded by the Webmin development list at webmin-devel <at> webmin.com
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-devel
Permalink | Reply | 4 comments |
headers
Jamie Cameron | 18 May 2003 04:11

Re: [webmin-devel] Module RPM naming convention

Joe Cooper wrote:
> Hey Jamie and all,
> 
> I know I've seen you mention this somewhere before, but I can't recall 
> the specifics.
> 
> What naming convention is Webmin looking for when installing a module 
> from RPM using the Webmin Modules module?  I'm rebuilding all of my 
> module RPMs for Red Hat 9, and would like to get it right this time.  ;-)

They have to be named wbm-<modulename> , such as wbm-ppp-client . I 
have a script that can construct such an RPM from a module directory 
if you are planning on building a few.. The %post script of the RPM 
has to follow certain standards, like adding themselves to the 
/etc/webmin/webmin.acl file and copying config files to 
/etc/webmin/≤modulename> .

  - Jamie

-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
-
Forwarded by the Webmin development list at webmin-devel <at> webmin.com
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-devel
(Continue reading)

Permalink | Reply | 3 comments |
headers
Joe Cooper | 18 May 2003 04:51

Re: [webmin-devel] Module RPM naming convention

Jamie Cameron wrote:
> Joe Cooper wrote:
> 
>> Hey Jamie and all,
>>
>> I know I've seen you mention this somewhere before, but I can't recall 
>> the specifics.
>>
>> What naming convention is Webmin looking for when installing a module 
>> from RPM using the Webmin Modules module?  I'm rebuilding all of my 
>> module RPMs for Red Hat 9, and would like to get it right this time.  ;-)
> 
> 
> They have to be named wbm-<modulename> , such as wbm-ppp-client . I have 
> a script that can construct such an RPM from a module directory if you 
> are planning on building a few.. The %post script of the RPM has to 
> follow certain standards, like adding themselves to the 
> /etc/webmin/webmin.acl file and copying config files to 
> /etc/webmin/≤modulename> .

I have quite a few custom modules that I package, and I have a template 
spec file that I use, but it does leave a few installation steps out, so 
I have to finish up manually (mainly just making the module visible to 
those users who need to see it).  So, a script to auto-generate would be 
cool.

But perhaps rather than sending via email, you should post it to the 
devel page?  I guess I'm not the only one making RPMs of custom modules 
on a regular basis.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jamie Cameron | 18 May 2003 04:58

Re: [webmin-devel] Module RPM naming convention

Joe Cooper wrote:
> Jamie Cameron wrote:
> 
>> Joe Cooper wrote:
>>
>>> Hey Jamie and all,
>>>
>>> I know I've seen you mention this somewhere before, but I can't 
>>> recall the specifics.
>>>
>>> What naming convention is Webmin looking for when installing a module 
>>> from RPM using the Webmin Modules module?  I'm rebuilding all of my 
>>> module RPMs for Red Hat 9, and would like to get it right this time.  
>>> ;-)
>>
>>
>>
>> They have to be named wbm-<modulename> , such as wbm-ppp-client . I 
>> have a script that can construct such an RPM from a module directory 
>> if you are planning on building a few.. The %post script of the RPM 
>> has to follow certain standards, like adding themselves to the 
>> /etc/webmin/webmin.acl file and copying config files to 
>> /etc/webmin/≤modulename> .
> 
> 
> I have quite a few custom modules that I package, and I have a template 
> spec file that I use, but it does leave a few installation steps out, so 
> I have to finish up manually (mainly just making the module visible to 
> those users who need to see it).  So, a script to auto-generate would be 
> cool.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joe Cooper | 19 May 2003 02:06

Re: [webmin-devel] Module RPM naming convention

Jamie Cameron wrote:
> Joe Cooper wrote:

>> But perhaps rather than sending via email, you should post it to the 
>> devel page?  I guess I'm not the only one making RPMs of custom 
>> modules on a regular basis.
> 
> 
> Actually, I just noticed that it is already on the devel page under
> http://www.webmin.com/modules.html#wbm
> :-)

Perfect!  I've been reading the page so long I'm blind to what's on it. ;-)
--

-- 
Joe Cooper <joe <at> swelltech.com>
Web caching appliances and support.
http://www.swelltech.com

-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
-
Forwarded by the Webmin development list at webmin-devel <at> webmin.com
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-devel
Permalink | Reply | 0 comments |
headers
Clemens Oertel | 23 May 2003 02:05
Picon
Picon

[webmin-devel] Question useradmin layout

Hi alltogether,

while trying to write some to code to synchronize users among multiple 
machines upon creation/modification/deletion, I noticed that many 
functionality lies in the corresponding .cgi-files, not in the user-lib.pl.

My naive idea was to have a useradmin_update.pl file on the master machine, 
with something like:

&remote_foreign_call('my_user_synchronizer', 'create', %{$user_reference});

and on the client machines a module called my_user_synchronizer with a 
lib-file containing:

sub create {
	my (%user) =  <at> _;

	...
	&foreign_call('useradmin', 'create_user', \%user);
	&foreign_call('useradmin', 'make_changes');
	...
}

Works great, user gets created (or deleted or whatever).
However, this way I'm missing all the extended functionality, such as 
group changes, home dir movings etc. I also don't want to cut'n'paste code out 
of the respective cgi-scripts (maintainability ...).

So it occured to me that clean one-function interfaces for each of the user 
maintenance tasks (create, modify, delete) would be the perfect solution.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane