naviserver-devel — Developer discussion

Re: [naviserver-devel] Ns_conn location questions

[Gustaf N. <ne...@wu...>]

 > My first question is where this localhost comes from?

I would think, this comes from your configuration file and/of from the 
request.

If one starts e.g. with the sample configuration file nsd-config.tcl, 
one sees entries like:

     [29/Jan/2023:16:35:24][54720.100490580][-main:default-] Notice: nssock:0: adding virtual host entry for host <localhost:8080> location:http://localhost:8080  mapped to server: default ctx 0x0
     [29/Jan/2023:16:35:24][54720.100490580][-main:default-] Notice: nssock:0: adding virtual host entry for host <MacBook-Pro-6.local:8080> location:http://MacBook-Pro-6.local:8080  mapped to server: default ctx 0x0

These log-entries are coming e.g. from the following section

     ns_section ns/module/nssock/servers {
         ns_param default    localhost
         ns_param default    [ns_info hostname]
     }

from the configuration file that define the mapping of hostnames for the 
"default" server. When there are incoming requests following HTTP/1.1, 
these come with a "Host:" header field, which might be in your case as 
well "localhost".


 > When I try to run ns_conn location in nsshell it gives me error 
bad_option "location".

This is a know limitation (see first line of "Current shortcomings" on
https://bitbucket.org/naviserver/nsshell/src/main/

The reason for this is that nsshell communicates with a "kernel" thread 
in the background that keeps the state of your nsshell session (e.g. to 
be able to obtain the variable value for later requests, if one types 
"set x 1" in nsshell). Since this kernel runs in the background, it is 
no connection thread, and has no connection information available.

Theoretically, one could stretch the limits of nsshell further, but it 
is quite hard to make the background job look completely like the a 
connection thread.

-gn

[naviserver-devel] Ns_conn location questions

[Maksym Z. <siq...@gm...>]

Hello, I have some questions about ns_conn location.
According to manual "The location is determined via the following means:

1. if *ns_locationproc
<https://naviserver.sourceforge.io/n/naviserver/files/ns_locationproc.html>*
is configured, its result is returned.
2. if virtual hosting is enabled, and the "Host:" header field is provided
and valid, it returns its content.
3. If everything above fails, it is determined by virtual hosts mapping
table (as defined in the "ns/module/nssock/servers" or
"ns/module/nsssl/servers" section in the configuration file).
4. If everything above fails, and a connection is open, it is determined by
the current socket address.
5. If everything above fails, it is determined by configuration values of
the driver."

First and second is not my case, because i'm not using virtual hosting, in
my config i have part like that:

ns_section "ns/module/nsssl" {
ns_param defaultserver $hostname
ns_param address $ip_addr
ns_param port $ssl_port
ns_param hostnamens_section "ns/module/nsssl" {
ns_param defaultserver $hostname
ns_param certificate /opt/ns/modules/nsssl/daidze.pem
ns_param address $ip_addr
ns_param port $ssl_port
ns_param hostname $hostname
...
}

So I'm assuming i'm gonna get $hostname:$ssl_port when i run [ns_conn
location]
I'm running Naviserver inside Docker container, and instead getting
localhost.

My first question is where this localhost comes from?

And second question when I try to run ns_conn location in nsshell it gives
me error bad_option "location". Actually it gives this error when I try to
run any subcommand of ns_conn inside nsshell.

Thank you

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Gustaf N. <ne...@wu...>]

Dear Wolfgang,

After Maksym Zinchenko, we found as well a problem with the modified ADP 
parser (inside an embedded minified JavaScript code)

The situation is more tricky than expected, since we have
- a language mix in ADP files (Tcl, HTML, JavaScript) and special ADP 
tags and semantics
- Some of these problems are addressed by HTML, which treats <script>
    context as CDATA (e.g. tags inside JavaScript)

      <script type="text/javascript">document.write("<script>alert('Hi')</script>");</script>
      <script type="text/javascript">x = '<br>';</script>

   In addition, ADP allows as well inline code blocks

     <script type="text/javascript"> x= '<%= [expr {2 + 2}] %>';</script>

  such that CDATA is not sufficient. Some of the <script>s can be 
executed on the client side, some on the server side (runat=server), and 
ADP also supports tag substitutions in tag definitions as well

   <html<if @doc.lang@ not nil> lang="@doc.lang;literal@"</if>>
   <script type="@type@"<if @src@ not nil> src="@src@"</if>><if @content@ not nil>@content@</if></script>

These are examples from OpenACS, which as an <if> tag defined and has 
also special substitution rules. The usage of ADP tags inside the 
starting HTML tags is not really documented, but used all over.

The semantics of the ADP parser are quite complex to handle these 
situations in some meaningful way, and i would not be surprised, if some 
rough edges limit full orthogonality would pop up. However, the version 
committed today addresses all known issues, and has a substantially 
extended regression test. It required some refactoring of the ADP 
parser. The performance should be slightly faster than the classical parser.

Please test if possible,

-g

Re: [naviserver-devel] invalid command name "detach" used within example documentation

[Gustaf N. <ne...@wu...>]

Dear David,

this is a documentation bug. What i can see by digging into old 
versions, the command "detach" was removed between AOLserver 3 and 4.... 
but survived in the documentation.

Not sure, someone has an example of a server based on ns_socket, but i 
have written several years ago a (partial) implementation of an ftp 
server based on ns_connchan (see attachment). We do not have this in 
active use, but maybe you can use this as a blueprint for your project.

all the best

-gn

On 15.01.23 20:22, D.Fox wrote:
> Greetings, I was trying to setup a socket server within NaviServer.
>
> Following the example listed under ns_sockcallback within the 
> documentation. The example uses an detach procedure although when I 
> attempt to use the syntax I get an invalid command name error
>
> https://naviserver.sourceforge.io/n/naviserver/files/ns_sockcallback.html
>
> failed: invalid command name "detach"
> :    TCL LOOKUP COMMAND detach
> :    invalid command name "detach"
> :        while executing
> :    "detach $sock"
> :        (file "Init.tcl" line 25)
> :        invoked from within
> :    "source $file"
>
> If I remove the detach, it creates the socket server however this only 
> allows one connection and then refuses to initiate any other 
> connections there after.
> Any insight would be great on how to allow multiple connections.
>
> Many Thanks,
> David Fox
>
>
>
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

-- 
Univ.Prof. Dr. Gustaf Neumann
Head of the Institute of Information Systems and New Media
of Vienna University of Economics and Business
Program Director of MSc "Information Systems"

[naviserver-devel] invalid command name "detach" used within example documentation

[D.Fox <un...@cr...>]

Greetings, I was trying to setup a socket server within NaviServer. 

Following the example listed under ns_sockcallback within the documentation. The example uses an detach procedure although when I attempt to use the syntax I get an invalid command name error 

[ https://naviserver.sourceforge.io/n/naviserver/files/ns_sockcallback.html | https://naviserver.sourceforge.io/n/naviserver/files/ns_sockcallback.html ] 

failed: invalid command name "detach" 
: TCL LOOKUP COMMAND detach 
: invalid command name "detach" 
: while executing 
: "detach $sock" 
: (file "Init.tcl" line 25) 
: invoked from within 
: "source $file" 

If I remove the detach, it creates the socket server however this only allows one connection and then refuses to initiate any other connections there after. 
Any insight would be great on how to allow multiple connections. 

Many Thanks, 
David Fox 

Re: [naviserver-devel] nsshell

[Gustaf N. <ne...@wu...>]

Hi Maksym,

This was due to the change of yesterday triggered by Wolfgang's report.
NaviServer's parser handles <% ... %> blocks also as tags, but in such
cases, the quote handling should not be applied. For now, I've added a
quick fix to fall back to the old behavior in such blocks, ... and added
a test case for such condition. Probably, the code should be more
refactored, when I have some more time.

Please update, nsshell should work again as before.

all the best

-g

On 06.01.23 11:44, Maksym Zinchenko wrote:
> Hello, I'm having trouble after update naviserver with shell, it shows
...

[naviserver-devel] nsshell

[Maksym Z. <siq...@gm...>]

Hello, I'm having trouble after update naviserver with shell, it shows

>
> <% # Get hostname without protocol (i.e. "localhost") set host [lindex
> [split [ns_conn location] "/"] 2] set wsConfigPath "ns/server/[ns_info
> server]/module/websocket/shell" set shConfigPath "ns/server/[ns_info
> server]/module/nsshell" # Get WebSocket Protocol (i.e. "ws") set wsProtocol
> [expr {[ns_conn protocol] eq "http" ? "ws" : "wss"}] # Get Shell URL from
> module (i.e. "nsshell") set shellURL [ns_config $wsConfigPath urls] set
> heartBeat [ns_config $shConfigPath kernel_heartbeat 4] # Generate Base URL
> (i.e. "localhost/shell") set baseURL [string trimright $host/$shellURL] #
> Generate WebSocket URL (i.e. ws://localhost/shell/connect) set wsUri
> $wsProtocol://$baseURL/connect # Generate kernelId # Combine uuid with
> connection id and encrpyt with sha-1 set kernelID [ns_sha1 "[ns_uuid]
> [ns_conn id]"] # Remember ns_conn settings from the start of this shell #
> in a nsv variable for this kernel. foreach subcommand { acceptedcompression
> auth authpassword authuser contentfile contentlength contentsentlength
> driver files flags form headers host id isconnected location method
> outputheaders peeraddr peerport pool port protocol query partialtimes
> request server sock start timeout url urlc urlv version zipaccepted } {
> nsv_set shell_conn $kernelID,$subcommand [ns_conn $subcommand] } # # Check,
> if we are connected via the WebSocket interface or via XHR # if
> {${shellURL} ne "" && [string match ${shellURL}* [ns_conn url]]} { ns_log
> notice "nsshell uses WebSocket interface" # # Flag WebSocket usage by
> setting xhrURL empty. # set xhrURL "" # If kernelID is specified on URL,
> change kernelId to the one # specified in the URL if {"kernel" in [ns_conn
> urlv]} { set kernelID [string trim [lindex [ns_conn urlv] end]] # KernelID
> cannot empty if {$kernelID eq ""} { ns_returnredirect [ns_conn
> location]/$shellURL } } else { # If kernel isn't specified on URL, redirect
> with the generated kernelId ns_returnredirect [ns_conn
> location]/$shellURL/kernel/$kernelID } } else { ns_log notice "nsshell uses
> XHR interface" # # Flag XHR usage by setting wsUri empty. # set wsUri ""
> set xhrURL [ns_conn url] # If kernel is specified on URL, change kernelId
> to the URL one set query_kernelID [ns_queryget kernelID ""] if
> {$query_kernelID eq ""} { ns_returnredirect "[ns_conn
> url]?kernelID=$kernelID" } else { set kernelID $query_kernelID } } %>
>

In the browser window

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Wolfgang W. <wol...@di...>]

Aloha!

I'll test it over the weekend, including performance tests.

Mahalo and have a nice time in Maui!

Regards,

Wolfgang

Am 05.01.23 um 07:08 schrieb Gustaf Neumann:
>
> Dear Wolfgang,
>
> The HTML Living Standard allows the greater than sign inside single or 
> double quoted
> attribute values, so i would regard the old behavior as a bug (i think 
> to remember
> that at a certain time, one had to use entities for these).
>
> With the change, all old test continue to work, although the testing set
> is not very extensive. Please test.
>
> https://bitbucket.org/naviserver/naviserver/commits/6f7b322d0f45daa2154d702ca763442bb2be9fac
>
> all the best from Maui,
>
> -gustaf
>
> On 04.01.23 15:19, Wolfgang Winkler via naviserver-devel wrote:
>>
>> Hello!
>>
>> When we try to use custom tags with attributes, we encounter a 
>> problem when passing html strings, e.g:
>>
>> proc::dummy_tag_proc {params} {
>> return[ns_set array$params]
>> }
>> ns_adp_registerscript dummy_tag ::dummy_tag_proc
>>
>> <dummy_tag title="<i class='fal fa-link'></i>">
>>
>> Outputs:
>>
>> title {"<i class='fal fa-icon'>}
>>
>> Everything after the first ">" is truncated. Is there a safe way to 
>> prevent this behaviour?
>>
>> Regards,
>>
>> Wolfgang
>>
>> -- 
>>
>> *Wolfgang Winkler*
>> Geschäftsführung
>> wol...@di...
>> mobil +43.699.19971172
>>
>> dc:*büro*
>> digital concepts Novak Winkler OG
>> Software & Design
>> Landstraße 68, 5. Stock, 4020 Linz
>> www.digital-concepts.com <http://www.digital-concepts.com>
>> tel +43.732.997117.72
>> tel +43.699.1997117.2
>>
>> Firmenbuchnummer: 192003h
>> Firmenbuchgericht: Landesgericht Linz
>>
>>
>>
>>
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> -- 
> Univ.Prof. Dr. Gustaf Neumann
> Head of the Institute of Information Systems and New Media
> of Vienna University of Economics and Business
> Program Director of MSc "Information Systems"
>
>
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
-- 

*Wolfgang Winkler*
Geschäftsführung
wol...@di...
mobil +43.699.19971172

dc:*büro*
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com <http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Gustaf N. <ne...@wu...>]

Dear Wolfgang,

The HTML Living Standard allows the greater than sign inside single or 
double quoted
attribute values, so i would regard the old behavior as a bug (i think 
to remember
that at a certain time, one had to use entities for these).

With the change, all old test continue to work, although the testing set
is not very extensive. Please test.

https://bitbucket.org/naviserver/naviserver/commits/6f7b322d0f45daa2154d702ca763442bb2be9fac

all the best from Maui,

-gustaf

On 04.01.23 15:19, Wolfgang Winkler via naviserver-devel wrote:
>
> Hello!
>
> When we try to use custom tags with attributes, we encounter a problem 
> when passing html strings, e.g:
>
> proc::dummy_tag_proc {params} {
> return[ns_set array$params]
> }
> ns_adp_registerscript dummy_tag ::dummy_tag_proc
>
> <dummy_tag title="<i class='fal fa-link'></i>">
>
> Outputs:
>
> title {"<i class='fal fa-icon'>}
>
> Everything after the first ">" is truncated. Is there a safe way to 
> prevent this behaviour?
>
> Regards,
>
> Wolfgang
>
> -- 
>
> *Wolfgang Winkler*
> Geschäftsführung
> wol...@di...
> mobil +43.699.19971172
>
> dc:*büro*
> digital concepts Novak Winkler OG
> Software & Design
> Landstraße 68, 5. Stock, 4020 Linz
> www.digital-concepts.com <http://www.digital-concepts.com>
> tel +43.732.997117.72
> tel +43.699.1997117.2
>
> Firmenbuchnummer: 192003h
> Firmenbuchgericht: Landesgericht Linz
>
>
>
>
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

-- 
Univ.Prof. Dr. Gustaf Neumann
Head of the Institute of Information Systems and New Media
of Vienna University of Economics and Business
Program Director of MSc "Information Systems"

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Brian F. <bri...@ai...>]

Hi Wolfgang

I think that you need to use the endtag optional parameter to ns_adp_registerscript i.e. see https://naviserver.sourceforge.io/n/naviserver/files/ns_adp_register.html

Brian
________________________________
From: Wolfgang Winkler via naviserver-devel <nav...@li...>
Sent: Wednesday 4 January 2023 2:19 pm
To: Navidevel <nav...@li...>
Cc: Wolfgang Winkler <wol...@di...>
Subject: [naviserver-devel] ns_adp_registerproc and attributes


Hello!

When we try to use custom tags with attributes, we encounter a problem when passing html strings, e.g:

proc ::dummy_tag_proc {params} {
  return [ns_set array $params]
}
ns_adp_registerscript dummy_tag ::dummy_tag_proc

<dummy_tag title="<i class='fal fa-link'></i>">

Outputs:

title {"<i class='fal fa-icon'>}

Everything after the first ">" is truncated. Is there a safe way to prevent this behaviour?

Regards,

Wolfgang

--

Wolfgang Winkler
Geschäftsführung
wol...@di...<mailto:wol...@di...>
mobil +43.699.19971172

dc:büro
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com<http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

[https://www.digital-concepts.com/cu/digitalconcepts2016/images/logo_digitalconcepts2016.png]

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Brian F. <bri...@ai...>]

Hi Wolfgang

oh yes, I understand better now that your issue is with the HTML being included in the tag attributes. Nothing to do with endtags.
Are you sure you proc is correct? Maybe try something like this:

proc ::dummy_tag_proc {params} {
  set title [ns_set get $params title]
  return "My title is $title"
}

Brian
________________________________
From: Wolfgang Winkler via naviserver-devel <nav...@li...>
Sent: Wednesday 4 January 2023 3:20 pm
To: Navidevel <nav...@li...>
Cc: Wolfgang Winkler <wol...@di...>
Subject: Re: [naviserver-devel] ns_adp_registerproc and attributes


Hi Brian!


With the closing tag, it's possible to create custom tags like:


<dummy_tag title="<h1>My Title</h1>">

  <p>Output this text</p>

</dummy_tag>


and proc ::dummy_tag_proc {params inner_html} {

...

}


The inner_html parameter works fine, but the attribute values will be truncated as well, if a ">" sign is encountered.


Regards,


Wolfgang



Am 04.01.23 um 15:57 schrieb Brian Fenton:
Hi Wolfgang

I think that you need to use the endtag optional parameter to ns_adp_registerscript i.e. see https://naviserver.sourceforge.io/n/naviserver/files/ns_adp_register.html

Brian
________________________________
From: Wolfgang Winkler via naviserver-devel <nav...@li...><mailto:nav...@li...>
Sent: Wednesday 4 January 2023 2:19 pm
To: Navidevel <nav...@li...><mailto:nav...@li...>
Cc: Wolfgang Winkler <wol...@di...><mailto:wol...@di...>
Subject: [naviserver-devel] ns_adp_registerproc and attributes


Hello!

When we try to use custom tags with attributes, we encounter a problem when passing html strings, e.g:

proc ::dummy_tag_proc {params} {
  return [ns_set array $params]
}
ns_adp_registerscript dummy_tag ::dummy_tag_proc

<dummy_tag title="<i class='fal fa-link'></i>">

Outputs:

title {"<i class='fal fa-icon'>}

Everything after the first ">" is truncated. Is there a safe way to prevent this behaviour?

Regards,

Wolfgang

--

Wolfgang Winkler
Geschäftsführung
wol...@di...<mailto:wol...@di...>
mobil +43.699.19971172

dc:büro
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com<http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

[https://www.digital-concepts.com/cu/digitalconcepts2016/images/logo_digitalconcepts2016.png]

--

Wolfgang Winkler
Geschäftsführung
wol...@di...<mailto:wol...@di...>
mobil +43.699.19971172

dc:büro
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com<http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

[https://www.digital-concepts.com/cu/digitalconcepts2016/images/logo_digitalconcepts2016.png]

Re: [naviserver-devel] ns_adp_registerproc and attributes

[Wolfgang W. <wol...@di...>]

Hi Brian!


With the closing tag, it's possible to create custom tags like:


<dummy_tag title="<h1>My Title</h1>">

   <p>Output this text</p>

</dummy_tag>


and proc ::dummy_tag_proc {params inner_html} {

...

}


The inner_html parameter works fine, but the attribute values will be 
truncated as well, if a ">" sign is encountered.


Regards,


Wolfgang



Am 04.01.23 um 15:57 schrieb Brian Fenton:
> Hi Wolfgang
>
> I think that you need to use the endtag optional parameter to 
> ns_adp_registerscript i.e. see 
> https://naviserver.sourceforge.io/n/naviserver/files/ns_adp_register.html
>
> Brian
> ------------------------------------------------------------------------
> *From:* Wolfgang Winkler via naviserver-devel 
> <nav...@li...>
> *Sent:* Wednesday 4 January 2023 2:19 pm
> *To:* Navidevel <nav...@li...>
> *Cc:* Wolfgang Winkler <wol...@di...>
> *Subject:* [naviserver-devel] ns_adp_registerproc and attributes
>
> Hello!
>
> When we try to use custom tags with attributes, we encounter a problem 
> when passing html strings, e.g:
>
> proc::dummy_tag_proc {params} {
> return[ns_set array$params]
> }
> ns_adp_registerscript dummy_tag ::dummy_tag_proc
>
> <dummy_tag title="<i class='fal fa-link'></i>">
>
> Outputs:
>
> title {"<i class='fal fa-icon'>}
>
> Everything after the first ">" is truncated. Is there a safe way to 
> prevent this behaviour?
>
> Regards,
>
> Wolfgang
>
> -- 
>
> *Wolfgang Winkler*
> Geschäftsführung
> wol...@di... 
> <mailto:wol...@di...>
> mobil +43.699.19971172
>
> dc:*büro*
> digital concepts Novak Winkler OG
> Software & Design
> Landstraße 68, 5. Stock, 4020 Linz
> www.digital-concepts.com <http://www.digital-concepts.com>
> tel +43.732.997117.72
> tel +43.699.1997117.2
>
> Firmenbuchnummer: 192003h
> Firmenbuchgericht: Landesgericht Linz
>
>
-- 

*Wolfgang Winkler*
Geschäftsführung
wol...@di...
mobil +43.699.19971172

dc:*büro*
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com <http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

[naviserver-devel] ns_adp_registerproc and attributes

[Wolfgang W. <wol...@di...>]

Hello!

When we try to use custom tags with attributes, we encounter a problem 
when passing html strings, e.g:

proc::dummy_tag_proc {params} {
return[ns_set array$params]
}
ns_adp_registerscript dummy_tag ::dummy_tag_proc

<dummy_tag title="<i class='fal fa-link'></i>">

Outputs:

title {"<i class='fal fa-icon'>}

Everything after the first ">" is truncated. Is there a safe way to 
prevent this behaviour?

Regards,

Wolfgang

-- 

*Wolfgang Winkler*
Geschäftsführung
wol...@di...
mobil +43.699.19971172

dc:*büro*
digital concepts Novak Winkler OG
Software & Design
Landstraße 68, 5. Stock, 4020 Linz
www.digital-concepts.com <http://www.digital-concepts.com>
tel +43.732.997117.72
tel +43.699.1997117.2

Firmenbuchnummer: 192003h
Firmenbuchgericht: Landesgericht Linz

Re: [naviserver-devel] nsstats.tcl Process page fails on older Naviserver version

[Gustaf N. <ne...@wu...>]

Hi Brian,

many thanks for the patch, added on bitbucket!


all the best

-g

https://bitbucket.org/naviserver/nsstats/commits/7c8e69db4e83458f10bb8212b4111a60023d6693


On 28.11.22 17:49, Brian Fenton wrote:
> Hello
>
> I just tried the latest version of nsstats.tcl from 
> https://bitbucket.org/naviserver/nsstats/src/main/
> I have to say I love this tool, but in the latest version the Process 
> page is giving an error because our version of Naviserver doesn't 
> support "ns_conn details".

[naviserver-devel] nsstats.tcl Process page fails on older Naviserver version

[Brian F. <bri...@ai...>]

Hello

I just tried the latest version of nsstats.tcl from https://bitbucket.org/naviserver/nsstats/src/main/
I have to say I love this tool, but in the latest version the Process page is giving an error because our version of Naviserver doesn't support "ns_conn details".

I have patched as follows:
    try {
        set connect_info [ns_conn details]
        if {$connect_info ne ""} {
            append version_info ", connected via [ns_conn details]"
        }
        append version_info " from client [ns_conn peeraddr]"
    } on error {errmsg} {
        ns_log Notice "This version of Naviserver doesn't support ns_conn details: $errmsg"
    }

regards
Brian

Re: [naviserver-devel] Connecting to OpenSSL

[THORPE M. <ta...@me...>]

Hi Gustaf,

It just occurred to me that my comment about OpenSSL not being automatically configured by Naviserver was inappropriate. I was certainly not complaining and I completely understand that things change. My apologies. What that remark suggested was not my intention. 

Thorpe
> On Nov 8, 2022, at 00:37, Gustaf Neumann <ne...@wu...> wrote:
> 
> From your original mail, i got the impression that you hand no "issues" with NaviServer either, but you are wondering, why OpenSSL 3.* is not "picked up automatically" and still linked against OpenSSL 1.*.  Since there are many differences between OpenSSL 1.* and 3.* [1], many distributors do not replace the 1.* version upon installation of OpenSSL 3.* , but they install it side by side, simply to avoid problems (there are many API changes, see e.g. [2,3]). So, no all software compiled against the include files of OpenSSL 1.* will work out of the box with OpenSSL 3.*
> 
> Coming to my questions of the last mail: 
> - against which library is your nsd linked?
> - have you reconfigured and recompiled naviserver?
> 
> let me know, if i can be of any further help.
> 
> -g
> 
> [1] https://www.openssl.org/docs/man3.0/man7/migration_guide.html
> [2] https://packages.debian.org/bullseye/amd64/libssl1.1/filelist
> [3] https://packages.debian.org/bookworm/amd64/libssl3/filelist
> 
> On 07.11.22 14:52, THORPE MAYES via naviserver-devel wrote:
>> Hi Gustaf,
>> 
>> Thank you for your response and the information. 
>> 
>> I did not have any issues with previous OpenSSL updates, although I had not installed 3.x versions. 
>> 
>> Best regards. 
>> 
>> Thorpe
>> 
>> Thorpe Mayes
>> (512) 394-8766
>> 
>>> On 6 Nov 2022, at 11:34, Gustaf Neumann <ne...@wu...> <mailto:ne...@wu...> wrote:
>>>  Dear Thorpe,
>>> it looks like you have now two versions of openssl installed on your system, since the output "1.0.2k-fips" comes straight from the library. So, if you see this string, the library is still there. 
>>> 
>>> One can check the version used during linkage via
>>> 
>>>     ldd /usr/local/ns/bin/nsd
>>> 
>>> When upgrading to OpenSSL 3.*, it is recommended to recompile NaviServer
>>> (make clean, configure ..., make, make install) such that NaviServer can use 
>>> the newer library calls. When the path to the openssl libary is not specified
>>> explicitly, configure uses "pkg-config --libs openssl" to determine the 
>>> path the the library.
>>> 
>>> all the best
>>> 
>>> -g
>>> 
>>> PS Btw, OpenACS.org runs with OpenSSL 3.2.0-dev
>>> 
>>> On 06.11.22 13:47, THORPE MAYES via naviserver-devel wrote:
>>>> Hi,
>>>> 
>>>> I updated OpenSSL on my server to version 3.0.7.
>>>> 
>>>> Prior to updating, openssl version -a showed:
>>>> 
>>>> OpenSSL 1.0.2k-fips  26 Jan 2017
>>>> built on: reproducible build, date unspecified
>>>> platform: linux-x86_64
>>>> options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) 
>>>> compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
>>>> OPENSSLDIR: "/etc/pki/tls"
>>>> engines:  rdrand dynamic
>>>> 
>>>> After updating, openssl version -a showed:
>>>> 
>>>> OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
>>>> built on: Sat Nov  5 14:56:48 2022 UTC
>>>> platform: linux-x86_64
>>>> options:  bn(64,64)
>>>> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
>>>> OPENSSLDIR: "/etc/ssl"
>>>> ENGINESDIR: "/etc/ssl/lib64/engines-3"
>>>> MODULESDIR: "/etc/ssl/lib64/ossl-modules"
>>>> Seeding source: os-specific
>>>> CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9
>>>> 
>>>> When I restart naviserver I see this in the log file:
>>>> 
>>>> Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized
>>>> 
>>>> That is the previous version of OpenSSL on the server. 
>>>> 
>>>> What do I need to change in order for naviserver to use the current version of OpenSSL? Or, does it matter?
>>>> 
>>>> When I updated to naviserver version 4.99.24 my configuration was:
>>>> ./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib --enable-symbols
>>>> 
>>>> 
>>>> Thorpe
> 
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] Connecting to OpenSSL

[THORPE M. <ta...@me...>]

Hi Gustaf,

Thank you for your followup.

I have reconfigured and recompiled naviserver. I do not think I have any issues there. I have been able to update naviserver without any problems.

I installed openssl 3..0.7 again. The test showed a couple of errors. Very likely an issue.

I am using CentOS - 7. That could very well be an issue. 

I created a server using RockyLinux version 9.x. An earlier version of openssl 3.0 was already installed. I installed openssl 3.0.7. No errors. I stopped there for the moment. I will get a new server running using RockyLinux 9.x. That may very well solve my problem. If not, at least I will be working from a clean start.

You have been very helpful. Thank you. 

Best regards,

Thorpe

> On Nov 8, 2022, at 00:37, Gustaf Neumann <ne...@wu...> wrote:
> 
> From your original mail, i got the impression that you hand no "issues" with NaviServer either, but you are wondering, why OpenSSL 3.* is not "picked up automatically" and still linked against OpenSSL 1.*.  Since there are many differences between OpenSSL 1.* and 3.* [1], many distributors do not replace the 1.* version upon installation of OpenSSL 3.* , but they install it side by side, simply to avoid problems (there are many API changes, see e.g. [2,3]). So, no all software compiled against the include files of OpenSSL 1.* will work out of the box with OpenSSL 3.*
> 
> Coming to my questions of the last mail: 
> - against which library is your nsd linked?
> - have you reconfigured and recompiled naviserver?
> 
> let me know, if i can be of any further help.
> 
> -g
> 
> [1] https://www.openssl.org/docs/man3.0/man7/migration_guide.html
> [2] https://packages.debian.org/bullseye/amd64/libssl1.1/filelist
> [3] https://packages.debian.org/bookworm/amd64/libssl3/filelist
> 
> On 07.11.22 14:52, THORPE MAYES via naviserver-devel wrote:
>> Hi Gustaf,
>> 
>> Thank you for your response and the information. 
>> 
>> I did not have any issues with previous OpenSSL updates, although I had not installed 3.x versions. 
>> 
>> Best regards. 
>> 
>> Thorpe
>> 
>> Thorpe Mayes
>> (512) 394-8766
>> 
>>> On 6 Nov 2022, at 11:34, Gustaf Neumann <ne...@wu...> <mailto:ne...@wu...> wrote:
>>>  Dear Thorpe,
>>> it looks like you have now two versions of openssl installed on your system, since the output "1.0.2k-fips" comes straight from the library. So, if you see this string, the library is still there. 
>>> 
>>> One can check the version used during linkage via
>>> 
>>>     ldd /usr/local/ns/bin/nsd
>>> 
>>> When upgrading to OpenSSL 3.*, it is recommended to recompile NaviServer
>>> (make clean, configure ..., make, make install) such that NaviServer can use 
>>> the newer library calls. When the path to the openssl libary is not specified
>>> explicitly, configure uses "pkg-config --libs openssl" to determine the 
>>> path the the library.
>>> 
>>> all the best
>>> 
>>> -g
>>> 
>>> PS Btw, OpenACS.org runs with OpenSSL 3.2.0-dev
>>> 
>>> On 06.11.22 13:47, THORPE MAYES via naviserver-devel wrote:
>>>> Hi,
>>>> 
>>>> I updated OpenSSL on my server to version 3.0.7.
>>>> 
>>>> Prior to updating, openssl version -a showed:
>>>> 
>>>> OpenSSL 1.0.2k-fips  26 Jan 2017
>>>> built on: reproducible build, date unspecified
>>>> platform: linux-x86_64
>>>> options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) 
>>>> compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
>>>> OPENSSLDIR: "/etc/pki/tls"
>>>> engines:  rdrand dynamic
>>>> 
>>>> After updating, openssl version -a showed:
>>>> 
>>>> OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
>>>> built on: Sat Nov  5 14:56:48 2022 UTC
>>>> platform: linux-x86_64
>>>> options:  bn(64,64)
>>>> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
>>>> OPENSSLDIR: "/etc/ssl"
>>>> ENGINESDIR: "/etc/ssl/lib64/engines-3"
>>>> MODULESDIR: "/etc/ssl/lib64/ossl-modules"
>>>> Seeding source: os-specific
>>>> CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9
>>>> 
>>>> When I restart naviserver I see this in the log file:
>>>> 
>>>> Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized
>>>> 
>>>> That is the previous version of OpenSSL on the server. 
>>>> 
>>>> What do I need to change in order for naviserver to use the current version of OpenSSL? Or, does it matter?
>>>> 
>>>> When I updated to naviserver version 4.99.24 my configuration was:
>>>> ./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib --enable-symbols
>>>> 
>>>> 
>>>> Thorpe
> 
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] Connecting to OpenSSL

[Gustaf N. <ne...@wu...>]

 From your original mail, i got the impression that you hand no "issues" 
with NaviServer either, but you are wondering, why OpenSSL 3.* is not 
"picked up automatically" and still linked against OpenSSL 1.*.  Since 
there are many differences between OpenSSL 1.* and 3.* [1], many 
distributors do not replace the 1.* version upon installation of OpenSSL 
3.* , but they install it side by side, simply to avoid problems (there 
are many API changes, see e.g. [2,3]). So, no all software compiled 
against the include files of OpenSSL 1.* will work out of the box with 
OpenSSL 3.*

Coming to my questions of the last mail:
- against which library is your nsd linked?
- have you reconfigured and recompiled naviserver?

let me know, if i can be of any further help.

-g

[1] https://www.openssl.org/docs/man3.0/man7/migration_guide.html
[2] https://packages.debian.org/bullseye/amd64/libssl1.1/filelist
[3] https://packages.debian.org/bookworm/amd64/libssl3/filelist

On 07.11.22 14:52, THORPE MAYES via naviserver-devel wrote:
> Hi Gustaf,
>
> Thank you for your response and the information.
>
> I did not have any issues with previous OpenSSL updates, although I 
> had not installed 3.x versions.
>
> Best regards.
>
> Thorpe
>
> Thorpe Mayes
> (512) 394-8766
>
>> On 6 Nov 2022, at 11:34, Gustaf Neumann <ne...@wu...> wrote:
>>  Dear Thorpe,
>>
>> it looks like you have now two versions of openssl installed on your 
>> system, since the output "1.0.2k-fips" comes straight from the 
>> library. So, if you see this string, the library is still there.
>>
>> One can check the version used during linkage via
>>
>>     ldd /usr/local/ns/bin/nsd
>>
>> When upgrading to OpenSSL 3.*, it is recommended to recompile NaviServer
>> (make clean, configure ..., make, make install) such that NaviServer 
>> can use
>> the newer library calls. When the path to the openssl libary is not 
>> specified
>> explicitly, configure uses "pkg-config --libs openssl" to determine the
>> path the the library.
>>
>> all the best
>>
>> -g
>>
>> PS Btw, OpenACS.org runs with OpenSSL 3.2.0-dev
>>
>> On 06.11.22 13:47, THORPE MAYES via naviserver-devel wrote:
>>> Hi,
>>>
>>> I updated OpenSSL on my server to version 3.0.7.
>>>
>>> Prior to updating, openssl version -a showed:
>>>
>>> OpenSSL 1.0.2k-fips  26 Jan 2017
>>> built on: reproducible build, date unspecified
>>> platform: linux-x86_64
>>> options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) 
>>> idea(int) blowfish(idx)
>>> compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB 
>>> -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT 
>>> -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
>>> -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 
>>> -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack 
>>> -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
>>> -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM 
>>> -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM 
>>> -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
>>> OPENSSLDIR: "/etc/pki/tls"
>>> engines:  rdrand dynamic
>>>
>>> After updating, openssl version -a showed:
>>>
>>> OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
>>> built on: Sat Nov  5 14:56:48 2022 UTC
>>> platform: linux-x86_64
>>> options:  bn(64,64)
>>> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 
>>> -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
>>> -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
>>> OPENSSLDIR: "/etc/ssl"
>>> ENGINESDIR: "/etc/ssl/lib64/engines-3"
>>> MODULESDIR: "/etc/ssl/lib64/ossl-modules"
>>> Seeding source: os-specific
>>> CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9
>>>
>>> When I restart naviserver I see this in the log file:
>>>
>>> Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized
>>>
>>>
>>> That is the previous version of OpenSSL on the server.
>>>
>>> What do I need to change in order for naviserver to use the current 
>>> version of OpenSSL? Or, does it matter?
>>>
>>> When I updated to naviserver version 4.99.24 my configuration was:
>>> ./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib 
>>> --enable-symbols
>>>
>>>
>>> Thorpe

Re: [naviserver-devel] Connecting to OpenSSL

[THORPE M. <ta...@me...>]

Hi Gustaf,

Thank you for your response and the information. 

I did not have any issues with previous OpenSSL updates, although I had not installed 3.x versions. 

Best regards. 

Thorpe

Thorpe Mayes
(512) 394-8766

> On 6 Nov 2022, at 11:34, Gustaf Neumann <ne...@wu...> wrote:
> 
> 
> Dear Thorpe,
> 
> it looks like you have now two versions of openssl installed on your system, since the output "1.0.2k-fips" comes straight from the library. So, if you see this string, the library is still there. 
> 
> One can check the version used during linkage via
> 
>     ldd /usr/local/ns/bin/nsd
> 
> When upgrading to OpenSSL 3.*, it is recommended to recompile NaviServer
> (make clean, configure ..., make, make install) such that NaviServer can use 
> the newer library calls. When the path to the openssl libary is not specified
> explicitly, configure uses "pkg-config --libs openssl" to determine the 
> path the the library.
> 
> all the best
> 
> -g
> 
> PS Btw, OpenACS.org runs with OpenSSL 3.2.0-dev
> 
> On 06.11.22 13:47, THORPE MAYES via naviserver-devel wrote:
>> Hi,
>> 
>> I updated OpenSSL on my server to version 3.0.7.
>> 
>> Prior to updating, openssl version -a showed:
>> 
>> OpenSSL 1.0.2k-fips  26 Jan 2017
>> built on: reproducible build, date unspecified
>> platform: linux-x86_64
>> options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) 
>> compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
>> OPENSSLDIR: "/etc/pki/tls"
>> engines:  rdrand dynamic
>> 
>> After updating, openssl version -a showed:
>> 
>> OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
>> built on: Sat Nov  5 14:56:48 2022 UTC
>> platform: linux-x86_64
>> options:  bn(64,64)
>> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
>> OPENSSLDIR: "/etc/ssl"
>> ENGINESDIR: "/etc/ssl/lib64/engines-3"
>> MODULESDIR: "/etc/ssl/lib64/ossl-modules"
>> Seeding source: os-specific
>> CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9
>> 
>> When I restart naviserver I see this in the log file:
>> 
>> Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized
>> 
>> That is the previous version of OpenSSL on the server. 
>> 
>> What do I need to change in order for naviserver to use the current version of OpenSSL? Or, does it matter?
>> 
>> When I updated to naviserver version 4.99.24 my configuration was:
>> ./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib --enable-symbols
>> 
>> 
>> Thorpe
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] Connecting to OpenSSL

[Gustaf N. <ne...@wu...>]

Dear Thorpe,

it looks like you have now two versions of openssl installed on your 
system, since the output "1.0.2k-fips" comes straight from the library. 
So, if you see this string, the library is still there.

One can check the version used during linkage via

     ldd /usr/local/ns/bin/nsd

When upgrading to OpenSSL 3.*, it is recommended to recompile NaviServer
(make clean, configure ..., make, make install) such that NaviServer can 
use
the newer library calls. When the path to the openssl libary is not 
specified
explicitly, configure uses "pkg-config --libs openssl" to determine the
path the the library.

all the best

-g

PS Btw, OpenACS.org runs with OpenSSL 3.2.0-dev

On 06.11.22 13:47, THORPE MAYES via naviserver-devel wrote:
> Hi,
>
> I updated OpenSSL on my server to version 3.0.7.
>
> Prior to updating, openssl version -a showed:
>
> OpenSSL 1.0.2k-fips  26 Jan 2017
> built on: reproducible build, date unspecified
> platform: linux-x86_64
> options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) 
> idea(int) blowfish(idx)
> compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB 
> -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT 
> -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
> -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 
> -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack -DPURIFY 
> -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
> -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM 
> -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM 
> -DGHASH_ASM -DECP_NISTZ256_ASM
> OPENSSLDIR: "/etc/pki/tls"
> engines:  rdrand dynamic
>
> After updating, openssl version -a showed:
>
> OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
> built on: Sat Nov  5 14:56:48 2022 UTC
> platform: linux-x86_64
> options:  bn(64,64)
> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 
> -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
> -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
> OPENSSLDIR: "/etc/ssl"
> ENGINESDIR: "/etc/ssl/lib64/engines-3"
> MODULESDIR: "/etc/ssl/lib64/ossl-modules"
> Seeding source: os-specific
> CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9
>
> When I restart naviserver I see this in the log file:
>
> Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized
>
>
> That is the previous version of OpenSSL on the server.
>
> What do I need to change in order for naviserver to use the current 
> version of OpenSSL? Or, does it matter?
>
> When I updated to naviserver version 4.99.24 my configuration was:
> ./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib 
> --enable-symbols
>
>
> Thorpe

[naviserver-devel] Connecting to OpenSSL

[THORPE M. <ta...@me...>]

Hi,

I updated OpenSSL on my server to version 3.0.7.

Prior to updating, openssl version -a showed:

OpenSSL 1.0.2k-fips  26 Jan 2017
built on: reproducible build, date unspecified
platform: linux-x86_64
options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) 
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches   -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
OPENSSLDIR: "/etc/pki/tls"
engines:  rdrand dynamic

After updating, openssl version -a showed:

OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)
built on: Sat Nov  5 14:56:48 2022 UTC
platform: linux-x86_64
options:  bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DNDEBUG
OPENSSLDIR: "/etc/ssl"
ENGINESDIR: "/etc/ssl/lib64/engines-3"
MODULESDIR: "/etc/ssl/lib64/ossl-modules"
Seeding source: os-specific
CPUINFO: OPENSSL_ia32cap=0xfffa3203478bffff:0x7a9

When I restart naviserver I see this in the log file:

Notice: OpenSSL OpenSSL 1.0.2k-fips  26 Jan 2017 initialized

That is the previous version of OpenSSL on the server. 

What do I need to change in order for naviserver to use the current version of OpenSSL? Or, does it matter?

When I updated to naviserver version 4.99.24 my configuration was:
./configure --prefix=/usr/local/ns --with-tcl=/usr/local/ns/lib --enable-symbols


Thorpe

[naviserver-devel] improved version introspection

[Gustaf N. <ne...@wu...>]

Dear all,

The "main" branch of NaviServer contains no more detailed version 
numbers to ease orientation, especially, when many installations are 
managed. The nstats process page contains now the OS, architecture, 
Tcl-version and the version of the OpenSSL library in use. The only 
interesting part missing is now the version of the Database (when in 
use), but that requires changes in the parent-driver of nsdb, where the 
concrete db-drivers have to report the information...

All the best

-gn


Provide introspection features for network driver

- ns_driver info: return in the resulting dict the additional field
   "libraryversion", which is supplied by network driver. This is at
   least useful for new installations and debugging, to make sure,
   which library is actually used

- "ns_conn details": new sub-command, returning a dict provided by a
   driver callback concerning the current connection. For an HTTPS
   connection, it returns the result of protocol and cipher
   negotiation, like e.g.

       {sslversion TLSv1.3 cipher TLS_AES_256_GCM_SHA384}

-- 
Univ.Prof. Dr. Gustaf Neumann
Head of the Institute of Information Systems and New Media
of Vienna University of Economics and Business
Program Director of MSc "Information Systems"

[naviserver-devel] Repository work: automated testing pipeline

[Gustaf N. <ne...@wu...>]

Dear all,

The NaviServer source code repository is now set up to run a CI/CD 
testing pipeline on every commit on the main and release/4.99 branches.
Since the free version of Bitbucket, where the repository is hosted, 
allows only limited resources (50 minutes per month), the commits are 
now forwarded to a GitHub mirror repository [1], which is more 
permissive (2000 minutes per month, but not only for NaviServer).
The CI/CD testing pipeline is built around docker images. On every run, 
we fetch ubuntu-latest, the necessary build-environment, Tcl sources, 
Tcllib, NSF, tDom, libthread, NaviServer, the PostgreSQL client library, 
and the nsdbpg module. Once everything is compiled successfully, the 
NaviServer regression test is performed (currently 1900 tests). This 
pipeline is just the initial version, more modules should be added in 
the future.
For the main and the release/4.99 branches, currently we test with two 
different compilers (gcc-10 and gcc-11), two Tcl versions (8.6.12 and 
8.7-a5), two versions of NSF/XOTcl (2.3.0 and 2.4.0) and with two 
different tDom versions (0.9.1 and 0.9.3):
- os: ubuntu-latest compiler: gcc-10 tcltag: core-8-6-12 nsf_version: 
2.3.0 tdom_version: 0.9.1 - os: ubuntu-latest compiler: gcc-11 tcltag: 
core-8-7-a5 nsf_version: 2.4.0 tdom_version: 0.9.3
You can see the results of these runs under [2].
Note that the naviserver-mirror repository is just set up for the 
testing pipeline. All development continues to happen on Bitbucket.
All the best
-gustaf neumann
[1] https://github.com/nm-wu/naviserver-mirror [2] 
https://github.com/nm-wu/naviserver-mirror/actions

[naviserver-devel] Repository work: Renaming default branch from "master" to "main"

[Gustaf N. <ne...@wu...>]

Dear all, The default branch of NaviServer was changed from "master" to 
"main". I have done this for the "naviserver" main repository and for 
the 51 modules below. Fresh checkouts are now on the branch "main", old 
checkouts should switch to the main branch after a "git pull" with: git 
branch main Since git 2.28, one can also change the default branch with 
the built-in git command: git config --global init.defaultBranch main We 
were actually quite late with this change. Details for the main branch 
reaming are here: 
https://dev.to/lukeocodes/change-git-s-default-branch-from-master-19le 
All the best -g Changed modules: letsencrypt nsaccess nsaspell nsauthpam 
nschartdir nsclamav nscoap nsconf nsdbbdb nsdbi nsdbilite nsdbimy 
nsdbipg nsdbmysql nsdbpg nsdbsqlite nsdbtds nsdhcpd nsdns nsexample 
nsexpat nsfortune nsgdchart nsicmp nsimap nsldap nsldapd nsloopctl 
nsmemcache nsocaml nsodbc nsoracle nsphp nsradiusd nsrtsp nssavi nsshell 
nssip nssmtpd nssnmp nsstats nssys nssyslogd nstftpd nstk nsudp nsvfs 
nswebpush nszlib revproxy websocket

Re: [naviserver-devel] ns_returnfile return original file name

[Oscar R. F. <oro...@vr...>]

I didn't know that.

It seems that most browsers are quite benevolent parsing this with
wrong space character encoding.

I have to update my code. 

Thank you very much! 

-----Mensaje original-----
De: Gustaf Neumann <ne...@wu...>
Responder a: nav...@li...
Para: nav...@li...
Asunto: Re: [naviserver-devel] ns_returnfile return original file
name
Fecha: Wed, 20 Jul 2022 22:08:05 +0200

Dear Oscar,
In principle, you are right concerning the encoding. A few comments:

- on most browsers, also utf-8 filenames are accepted,
   but the use of UTF-8 in the header fields is not recommended.

- For the percent encoding, one should use "ns_urlencode -path",
e.g., 

         ns_urlencode -part path {£ and € rates}

   since the "ns_urlencode" without parameters (as in your example)
uses a special rule for the space character.
One should actually provide an API along the lines of:
    ns_header_field_parameter -charset /charset/ -language /language/
name string
to ease its usage. ... maybe something for the next release...
All the best
-g
PS: Minor nitpick: RFC 5987 was obsoleted by RFC 8187
On 19.07.22 23:25, Oscar Rodriguez Fonseca wrote:
 
> Dear all,
> 
> Just for the sake of completeness. If you need an utf-8 encoded
> filename you may need to encode the filename (as per RFC 5987):
> 
> ns_set update [ns_conn outputheaders] Content-Disposition
> "attachment; filename*=UTF-8''[ns_urlencode $filename]"
> 
> ns_set update [ns_conn outputheaders] Content-Disposition
> "filename*=UTF-8''[ns_urlencode $filename]"
> 
> AFAIK it works well in any modern browser.
> 
> Best regards.
> 
> 
> -----Mensaje original-----
> De: Maksym Zinchenko <siq...@gm...>
> Responder a: nav...@li...
> Para: nav...@li...
> Asunto: Re: [naviserver-devel] ns_returnfile return original file
> name
> Fecha: Tue, 19 Jul 2022 16:33:58 -0100
> 
> Thank you all, that's exactly what I needed.
>  
> On Mon, Jul 18, 2022 at 1:00 PM Wolfgang Winkler via naviserver-
> devel <nav...@li...> wrote:
>  
> > Hi!
> > We use
> > ns_set update [ns_conn outputheaders] Content-Disposition
> > "attachment; filename=\"${filename}\""
> > for downloading and
> > ns_set update [ns_conn outputheaders] Content-Disposition
> > "filename=\"${filename}\""
> > for viewing files
> > Am 15.07.22 um 16:50 schrieb Maksym Zinchenko:
> >  
> >  
> > > Hello, I have a question about how to return the original file
> > > name. For example:
> > > 
> > > ns_register_proc GET /dev/rtrn_file ::dev::rtrn_file
> > >  proc rtrn_file {args} {
> > >  set f [file join /tmp test.csv]
> > >  ns_returnfile 200 [ns_guesstype "$f"] $f
> > >  }
> > > 
> > > When I do GET request  I'm getting "rtrn_file.csv" instead of
> > > "test.csv"
>  
>  
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
_______________________________________________
naviserver-devel mailing list
nav...@li...
https://lists.sourceforge.net/lists/listinfo/naviserver-devel