Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #5617 > unrolled thread

A GnuTLS-Problem - problems fetchin emails using RISC OS

Back to article view | Back to comp.sys.acorn.programmer

Contents

  A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-16 16:25 +0100
    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-17 11:32 +1300
      Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-17 00:25 +0100
        Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-17 13:25 +1300
          Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-17 18:45 +0100
            Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-18 09:27 +1300
              Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-18 12:03 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-19 18:57 +0100
                  Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-20 09:10 +1300
                    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-20 08:11 +0000
                  Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-20 00:00 -0800
                    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-20 19:03 +0100
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-20 19:52 +0000
                  Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 09:58 +1300
                    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 13:28 +1300
                      Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-21 00:39 -0800
                        Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 23:29 +1300
                          Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-22 04:11 +0100
                            Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 00:37 +1300
                  Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-22 04:16 +0100
                    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Martin <News03@avisoft.f9.co.uk> - 2018-12-22 11:34 +0000
                    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-22 17:16 +0000
                      Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 09:54 +1300
                        Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-22 21:23 +0000
                          Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-23 20:12 +0000
                        Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-22 21:59 +0000
                          Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 11:50 +1300
                            Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 14:35 +1300
                              Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-23 14:22 +0000
                                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-23 12:56 -0800
                            Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Matthew Phillips <spam2011m@yahoo.co.uk> - 2018-12-28 20:28 +0000
                              Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-29 12:10 +1300

Page 1 of 2  [1] 2  Next page →

#5617 — A GnuTLS-Problem - problems fetchin emails using RISC OS

People complaining that

http://home.chiemgau-net.de/ausserstorfer/Computer/POP3S16April2016GnuTLS3-4.zip
(840 kB) doesn't work on older machines (Risc PC).

I don't know what exactly the problem is. It may be that the ported
GnuTLS3.4 isn't compatible to the 26 bit instruction set. I don't know.

http://www.riscos.info/packages/LibraryDetails.html

I compile it using the commands

 gcc -O3 -static POP3S16Dec2018.c -o!RunImagePOP3S -ILibGNUTLS:
 -LLibGMP: -lgmp -LLibGNUTLS: -lgnutls -LLibGPGError: -lgpg-error
 -LLibNettle: -lhogweed -lnettle -LLibTASN1: -ltasn1 -LZlib1g: -lz
 -LLibGetText: -lintl

Some people cannot fetch their emails anymore using POP3S with an older
version of GnuTLS or !Hermes from Web.de here in Germany. May be that
the supported cipher suites are too old.

Thanks for your help!

Alex

-- 
http://home.chiemgau-net.de/ausserstorfer/
Mein Gott, warum hast du mich verlassen?

[toc] | [next] | [standalone]

#5621

In message <d7915c6757.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:

> People complaining that
> 
> http://home.chiemgau-net.de/ausserstorfer/Computer/POP3S16April2016GnuTLS3-4.zip
> (840 kB) doesn't work on older machines (Risc PC).
> 
> I don't know what exactly the problem is. It may be that the ported
> GnuTLS3.4 isn't compatible to the 26 bit instruction set. I don't know.
> 
> http://www.riscos.info/packages/LibraryDetails.html
> 
> I compile it using the commands
> 
>  gcc -O3 -static POP3S16Dec2018.c -o!RunImagePOP3S -ILibGNUTLS:
>  -LLibGMP: -lgmp -LLibGNUTLS: -lgnutls -LLibGPGError: -lgpg-error
>  -LLibNettle: -lhogweed -lnettle -LLibTASN1: -ltasn1 -LZlib1g: -lz
>  -LLibGetText: -lintl
> 
> Some people cannot fetch their emails anymore using POP3S with an older
> version of GnuTLS or !Hermes from Web.de here in Germany. May be that
> the supported cipher suites are too old.
> 
> Thanks for your help!
> 
> Alex
> 
Something similar happened to me while using !POP3S with gmail.
I rebuilt the autobuilder gnutls with the latest source available then
rebuilt on my Iyonix your source code and everything is still working to
this day.
Probably checking your version of gnutls, and maybe the autobuilder
could be fixed to a newer version than the default if necessary.
It could be that a newer version just has not been put in the
downloads area for too long? is that the one you are using?

The default GCCSDK builds for architecture V3 which should be fine for
older machines, I think there was little difference between v2 and v3 so
should be OK for older than Architecture V3 also.
Arch V3 started with A540/A5000 era, Arch V4 started with StrongArm
RiscPC, probably also the RISCOS 6 hardware?

Alan has uploaded OpenSSL1.1.1 to the autobuilder.
This version drops ssl3 and anything else insecure.

It comes with assembler routines for armv4 and newer.
So there is a boost for machines of x2 over default v3
The arm6 vfp version is faster again.

Running the optional testsuite:
Iyonix   with  armv3         650 seconds
Iyonix with armv4 (asm)      339 seconds
PiZero with arm6zk vfp       216 seconds

I have built my fetchmail port and an ssl version of curl without
problems so far.
A quick look on riscos.info and openssl1.1.1 isn't available as a
download yet.
I can put the versions up on my google drive for download if you wish
to try them?

Cheers, RonM.

[toc] | [prev] | [next] | [standalone]

#5622

Ron <gettingchoppy@gmail.com> wrote:

>> In message <d7915c6757.Eclipso@eclipso.at>
>>          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at>
>>          wrote:

> I rebuilt the autobuilder gnutls with the latest source available then
> rebuilt on my Iyonix your source code and everything is still working to
> this day.

Sorry. What is the autobuilder? I just have running both GCC and
DDE here.

> I can put the versions up on my google drive for download if you wish
> to try them?

That would be nice! Can you send me a link? Many thanks!

Ciao,

Alex

-- 
http://home.chiemgau-net.de/ausserstorfer/
Beachte bitte auch die Rückseite dieses Schreibens!

[toc] | [prev] | [next] | [standalone]

#5624

In message <827b886757.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:

> Ron <gettingchoppy@gmail.com> wrote:
> 
> >> In message <d7915c6757.Eclipso@eclipso.at>
> >>          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at>
> >>          wrote:
> 
> > I rebuilt the autobuilder gnutls with the latest source available then
> > rebuilt on my Iyonix your source code and everything is still working to
> > this day.
> 
> Sorry. What is the autobuilder? I just have running both GCC and
> DDE here.
> 
> > I can put the versions up on my google drive for download if you wish
> > to try them?
> 
> That would be nice! Can you send me a link? Many thanks!
> 
> Ciao,
> 
> Alex
> 
Ok I will start with just the !POP3S !Runfile I built with a later
gnutls.
If you say this works I will find the library I used and upload that.
If that does not work, I will have to try building a newer gnutls.

Will organise the 3 libssl versions over the next day also.

The link for the RISC_OS google drive directory is
https://drive.google.com/open?id=1TGAXW98WOXOjF5NSPKc2CelduSTxHvwx

I'm new to GoogleDrive, I think you need a javascript browser.
It will be interesting to see if I can add things to the folder
without needing to generate a new link.

Cheers RonM.

[toc] | [prev] | [next] | [standalone]

#5627

Ron <gettingchoppy@gmail.com> wrote:

> In message <827b886757.Eclipso@eclipso.at>
>          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:
>
>> Ron <gettingchoppy@gmail.com> wrote:

> Ok I will start with just the !POP3S !Runfile I built with a later
> gnutls.
> If you say this works I will find the library I used and upload that.

It works fine on the Raspberry Pi here

> If that does not work, I will have to try building a newer gnutls.

but not on the Risc PC:

POP3S - E-Mail-fetcher with TLS for RISC OS
Developer Version
09. July 2014

pop3.web.de

Fatal signal received: Illegal Instruction

Stack backtrace:

Running thread 0x194208
  ( 1bfff30) pc:   150e9c lr:   151340 sp:  1bfff34  __write_backtrace()
  ( 1bfffa0) pc:   150fb4 lr:   12c2b8 sp:  1bfffa4  __unixlib_raise_signal()
  ( 1bfffb0) pc:   12c1bc lr:    d5164 sp:  1bfe51c  __h_cback()

  Register dump at 01bfffb4:

    a1:   1b09b3 a2:   1b09b4 a3:  1bfe51c a4:        0
    v1:       1d v2:   1b09b3 v3:   1b09b3 v4:       1d
    v5: dec1c52e v6:   19002c sl:  1bfe208 fp:  1bfe584
    ip: cab7e4bc sp:  1bfe51c lr: 800d5164 pc: 600e492c
    Mode USR, flags set: nZCvif

  000e4918 : .@`å : e5604001 : STRB    R4,[R0,#-1]!
  000e491c : .0Sâ : e2533001 : SUBS    R3,R3,#1
  000e4920 : ùÿÿ. : 1afffff9 : BNE     &000E490C
  000e4924 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
  000e4928 : .ÿ/á : e12fff1e : BX      R14
  000e492c : .@qå : e5714001 : LDRB    R4,[R1,#-1]!
  000e4930 : .Prå : e5725001 : LDRB    R5,[R2,#-1]!
  000e4934 : .P%à : e0255004 : EOR     R5,R5,R4
  000e4938 : .P`å : e5605001 : STRB    R5,[R0,#-1]!

  ( 1bfe584) pc:    d50b8 lr:    b4800 sp:  1bfe588  nettle_salsa20r12_crypt()
  ( 1bfe62c) pc:    b4614 lr:    14510 sp:  1bfe630  wrap_nettle_rnd()
  ( 1bfe69c) pc:    143d0 lr:    195a8 sp:  1bfe6a0  send_client_hello()
  ( 1bfe6c8) pc:    1845c lr:     9200 sp:  1bfe6cc  gnutls_handshake()
  ( 1bfefec) pc:     8f04 lr:   139cb4 sp:  1bfeff0  main()

*

So we have with your version exactly the same problem as with the latest
one on my website which includes GnuTLS 3.4. My question is why this is
happen. With GnuTLS 2.12 it was working also on the Risc PC but this
version seems to not work with accounts of web.de anymore.

> Will organise the 3 libssl versions over the next day also.
>
> The link for the RISC_OS google drive directory is
> https://drive.google.com/open?id=1TGAXW98WOXOjF5NSPKc2CelduSTxHvwx

Thanks for the files. It doesn't work with !NetSurf here. It works also
very slow on my Asus Eee PC. I don't understand the sense of Google
drive. It produces a lot of traffic. A direct link like

http://home.chiemgau-net.de/ausserstorfer/Temp/2018-12-17/libgnutls-dev_3.5.8-1.zip
(2507 kB)

http://home.chiemgau-net.de/ausserstorfer/Temp/2018-12-17/pop3s_runimage.zip
(789 kB)

http://home.chiemgau-net.de/ausserstorfer/Temp/2018-12-17/smtps_runimage.zip
(788 kB)

would have been enough. These are your files so everybody can download
it now by just one click. It is so easy to do that. If it is a problem
for you, I will delete the files.

Thanks,

Alex

-- 
http://home.chiemgau-net.de/ausserstorfer/
Der Geist ist die Freiheit. (Frei.Wild)

[toc] | [prev] | [next] | [standalone]

#5628

In message <cd39ed6757.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:

> Ron <gettingchoppy@gmail.com> wrote:
> 
> > In message <827b886757.Eclipso@eclipso.at>
> >          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:
> >
> >> Ron <gettingchoppy@gmail.com> wrote:
> 
> > Ok I will start with just the !POP3S !Runfile I built with a later
> > gnutls.
> > If you say this works I will find the library I used and upload that.
> 
> It works fine on the Raspberry Pi here
> 
> > If that does not work, I will have to try building a newer gnutls.
> 
> but not on the Risc PC:
> 
It is odd that those !Runfiles are working on my Iyonix but not on the
RiscPC, I have seen a small C language mistake work OK on the Iyonix but
error on the Raspberry Pi once.
It is like the Iyonix is more tolerant.
I have not tried the libgnutls28_3.5.8-1.zip I uploaded.
I built it last night from debian stable but it is likely to be newer
than what I built my runfiles with. Could be worth trying building your
apps with it. The only other thing I can think of is to update the other
libraries in use, the backtrace shows a crash near a call to nettle or
crypt I think gnutls pulls in an external libcrypt so might be a problem
for all of the gnutls builds (new or old)

I dont mind you hosting the files, they'll have to be updated when we
fix them. Might have to label the current Runfiles 'Iyonix and newer'
but it sounds like they are no improvement over what you have anyway.

Re Google Drive,
Yes it's a bitch with Netsurf as it not only hides the shared folder but
also presents a login which acyually has nothing to do with what is
freely available when using javascript.
It is allowing me to upload files to the allready shared folder so for
public use, a bookmark of the link should always work.

Will rebuild crypt nettle with new stable then build libgnutls28 again.

Cheers RonM

[toc] | [prev] | [next] | [standalone]

#5631

In message <420ffc6757.beeb@-.->
          Ron <gettingchoppy@gmail.com> wrote:

> Will rebuild crypt nettle with new stable then build libgnutls28 again.
> 
> Cheers RonM
> 
OK I started from scratch and built all the libraries that are pulled in
by the libraries that are used in !POP3S
They are all from the current stable/stretch repository.
Should be at the same google drive link.

It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
often gets bigger.
Another idea would be to try the RiscPC using gcc without the optimise
flag.

Let us know if compiling with those libraries improves things.
Note that the gnutls28 is renewed/rebuilt also.

Cheers RonM.

[toc] | [prev] | [next] | [standalone]

#5636

Ron <gettingchoppy@gmail.com> wrote:

> In message <420ffc6757.beeb@-.->
>          Ron <gettingchoppy@gmail.com> wrote:
>
>> Will rebuild crypt nettle with new stable then build libgnutls28 again.
>>
>> Cheers RonM
>>
> OK I started from scratch and built all the libraries that are pulled in
> by the libraries that are used in !POP3S
> They are all from the current stable/stretch repository.
> Should be at the same google drive link.
>
> It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
> often gets bigger.
> Another idea would be to try the RiscPC using gcc without the optimise
> flag.
>
> Let us know if compiling with those libraries improves things.
> Note that the gnutls28 is renewed/rebuilt also.

Thank you very much for your help, support, work & time!

Here is what we got after starting the !Runimage file of

mail_applications -> armv3(all) -> pop3s-18th-dec.zip on a Risc PC 700
with StrongARM:

| POP3S - E-Mail-fetcher with TLS for RISC OS
| Developer Version 16. April 2016
| GnuTLS version 3.5.8
|
| pop3.web.de
|
| Fatal signal received: Illegal Instruction
|
| Stack backtrace:
|
| Running thread 0x1fba98 (Main Thread)
|   ( 1bfff30) pc:   181838 lr:   181ce4 sp:  1bfff34  __write_backtrace()
|   ( 1bfffa0) pc:   181958 lr:   15c408 sp:  1bfffa4  __unixlib_raise_signal()
|   ( 1bfffb0) pc:   15c30c lr:    f3e88 sp:  1bfe508  __h_cback()
|
|   Register dump at 01bfffb4:
|
|     a1:   2185db a2:   2185dc a3:  1bfe508 a4:        0
|     v1:       1d v2:   2185db v3:   2185db v4:       1d
|     v5: 1720a31a v6:   1f7808 sl:  1bfe208 fp:  1bfe570
|     ip: f76da8e4 sp:  1bfe508 lr: 800f3e88 pc: 600f2e40
|     Mode USR, flags set: nZCvif
|
|   000f2e2c : .@`å : e5604001 : STRB    R4,[R0,#-1]!
|   000f2e30 : .0Sâ : e2533001 : SUBS    R3,R3,#1
|   000f2e34 : ùÿÿ. : 1afffff9 : BNE     &000F2E20
|   000f2e38 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
|   000f2e3c : .ÿ/á : e12fff1e : BX      R14
|   000f2e40 : .@qå : e5714001 : LDRB    R4,[R1,#-1]!
|   000f2e44 : .Prå : e5725001 : LDRB    R5,[R2,#-1]!
|   000f2e48 : .P%à : e0255004 : EOR     R5,R5,R4
|   000f2e4c : .P`å : e5605001 : STRB    R5,[R0,#-1]!
|
|   ( 1bfe570) pc:    f3ddc lr:    b9594 sp:  1bfe574  nettle_salsa20r12_crypt()
|   ( 1bfe5bc) pc:    b9528 lr:    b994c sp:  1bfe5c0  wrap_nettle_rnd_nonce.isra.0()
|   ( 1bfe5cc) pc:    b9928 lr:    37be0 sp:  1bfe5d0  wrap_nettle_rnd()
|   ( 1bfe5f0) pc:    37b6c lr:    14d7c sp:  1bfe5f4  gnutls_rnd()
|   ( 1bfe684) pc:    14c20 lr:    1ae0c sp:  1bfe688  send_client_hello()
|   ( 1bfe6b0) pc:    19c58 lr:     9668 sp:  1bfe6b4  gnutls_handshake()
|   ( 1bfefec) pc:     9380 lr:   16a230 sp:  1bfeff0  main()
|
| *

I have now idea why this is happen and what's going on. It seems to run
properly on my Raspberry Pi, though.

Alex

-- 
http://home.chiemgau-net.de/ausserstorfer/
Humanitas sit lex suprema.

[toc] | [prev] | [next] | [standalone]

#5637

In message <5600f66857.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:

> Ron <gettingchoppy@gmail.com> wrote:
> 
> > In message <420ffc6757.beeb@-.->
> >          Ron <gettingchoppy@gmail.com> wrote:
> >
> >> Will rebuild crypt nettle with new stable then build libgnutls28 again.
> >>
> >> Cheers RonM
> >>
> > OK I started from scratch and built all the libraries that are pulled in
> > by the libraries that are used in !POP3S
> > They are all from the current stable/stretch repository.
> > Should be at the same google drive link.
> >
> > It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
> > often gets bigger.
> > Another idea would be to try the RiscPC using gcc without the optimise
> > flag.
> >
> > Let us know if compiling with those libraries improves things.
> > Note that the gnutls28 is renewed/rebuilt also.
> 
> Thank you very much for your help, support, work & time!
> 
> Here is what we got after starting the !Runimage file of
> 
> mail_applications -> armv3(all) -> pop3s-18th-dec.zip on a Risc PC 700
> with StrongARM:
> 
> | POP3S - E-Mail-fetcher with TLS for RISC OS
> | Developer Version 16. April 2016
> | GnuTLS version 3.5.8
> |
> | pop3.web.de
> |
> | Fatal signal received: Illegal Instruction
> |
> | Stack backtrace:
> |
> | Running thread 0x1fba98 (Main Thread)
> |   ( 1bfff30) pc:   181838 lr:   181ce4 sp:  1bfff34  __write_backtrace()
> |   ( 1bfffa0) pc:   181958 lr:   15c408 sp:  1bfffa4  __unixlib_raise_signal()
> |   ( 1bfffb0) pc:   15c30c lr:    f3e88 sp:  1bfe508  __h_cback()
> |
> |   Register dump at 01bfffb4:
> |
> |     a1:   2185db a2:   2185dc a3:  1bfe508 a4:        0
> |     v1:       1d v2:   2185db v3:   2185db v4:       1d
> |     v5: 1720a31a v6:   1f7808 sl:  1bfe208 fp:  1bfe570
> |     ip: f76da8e4 sp:  1bfe508 lr: 800f3e88 pc: 600f2e40
> |     Mode USR, flags set: nZCvif
> |
> |   000f2e2c : .@`å : e5604001 : STRB    R4,[R0,#-1]!
> |   000f2e30 : .0Sâ : e2533001 : SUBS    R3,R3,#1
> |   000f2e34 : ùÿÿ. : 1afffff9 : BNE     &000F2E20
> |   000f2e38 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
> |   000f2e3c : .ÿ/á : e12fff1e : BX      R14
> |   000f2e40 : .@qå : e5714001 : LDRB    R4,[R1,#-1]!
> |   000f2e44 : .Prå : e5725001 : LDRB    R5,[R2,#-1]!
> |   000f2e48 : .P%à : e0255004 : EOR     R5,R5,R4
> |   000f2e4c : .P`å : e5605001 : STRB    R5,[R0,#-1]!
> |
> |   ( 1bfe570) pc:    f3ddc lr:    b9594 sp:  1bfe574  nettle_salsa20r12_crypt()
> |   ( 1bfe5bc) pc:    b9528 lr:    b994c sp:  1bfe5c0  wrap_nettle_rnd_nonce.isra.0()
> |   ( 1bfe5cc) pc:    b9928 lr:    37be0 sp:  1bfe5d0  wrap_nettle_rnd()
> |   ( 1bfe5f0) pc:    37b6c lr:    14d7c sp:  1bfe5f4  gnutls_rnd()
> |   ( 1bfe684) pc:    14c20 lr:    1ae0c sp:  1bfe688  send_client_hello()
> |   ( 1bfe6b0) pc:    19c58 lr:     9668 sp:  1bfe6b4  gnutls_handshake()
> |   ( 1bfefec) pc:     9380 lr:   16a230 sp:  1bfeff0  main()
> |
> | *
> 
> I have now idea why this is happen and what's going on. It seems to run
> properly on my Raspberry Pi, though.
> 
> Alex
>
It still /appears/ to be a problem with nettle/gcrypt but I'm no good at
interpreting the machine code above that. Any advice from Druck?
Would running Armalyser on the libraries show any incompatible code?

The Dec18 !Runimage's are OK on my Iyonix also.
If you dont have a Strongarm machine at home it will be hard to try
different things. I might pull my one out of storage over the holidays.

There may be gcc options (suggestions anyone?) that could be tried. It
doesn't take long to compile each time, which is good.

It doesn't look like using different versions of the libraries has
helped, but at least the set at my google drive are all current stable
libs and not a mix of different eras.

The RiscPC does use a different memory system to RISC OS 5 but as long
as the wimpslot is big enough it shouldn't matter.
The !RunImage is over 2MB now.
I noticed if the wimpslot is close to the edge, it can fail when large
emails come through, just give it plenty (while testing anyway).

Ronald(NZ time)

[toc] | [prev] | [next] | [standalone]

#5639

On 19/12/2018 20:10, Ron wrote:
> In message <5600f66857.Eclipso@eclipso.at>
>            Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:
> 
>> Ron <gettingchoppy@gmail.com> wrote:
>>
>> |   000f2e3c : .ÿ/á : e12fff1e : BX      R14

>> I have now idea why this is happen and what's going on. It seems to run
>> properly on my Raspberry Pi, though.
>>
>> Alex
>>
> It still /appears/ to be a problem with nettle/gcrypt but I'm no good at
> interpreting the machine code above that. Any advice from Druck?
> Would running Armalyser on the libraries show any incompatible code?

You can see the incompatible code right there, its the BX instruction. 
It was originally a Thumb instruction, but is also in Thumb 2, which is 
supported by the ARMv6 and later processors in the Raspberry Pi, but not 
by processors in earlier machines such as the Risc PC and Iyonix.

The code needs to be recompiled to target ARMv3, to work with all Risc 
PCs and later, or ARMv4 for the StrongARM and later.

---druck

[toc] | [prev] | [next] | [standalone]

#5638

On Wednesday, 19 December 2018 17:58:43 UTC, Alexander Ausserstorfer  wrote:
> mail_applications -> armv3(all) -> pop3s-18th-dec.zip on a Risc PC 700
> with StrongARM:
> 
> | POP3S - E-Mail-fetcher with TLS for RISC OS
> | Developer Version 16. April 2016
> | GnuTLS version 3.5.8
> |   000f2e2c : .@`å : e5604001 : STRB    R4,[R0,#-1]!
> |   000f2e30 : .0Sâ : e2533001 : SUBS    R3,R3,#1
> |   000f2e34 : ùÿÿ. : 1afffff9 : BNE     &000F2E20
> |   000f2e38 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
> |   000f2e3c : .ÿ/á : e12fff1e : BX      R14
> 
> I have now idea why this is happen and what's going on. It seems to run
> properly on my Raspberry Pi, though.

This is the same problem (even the same instruction!) as I reported to you by email on 13-Aug-2018. BX R14 is an ARMv5 instruction, but the Risc PC is ARMv4 (if StrongARM) or ARMv3 (if ARM610/710), so you get an undefined instruction fault. 

I'm afraid I can't help figuring out which combination of switches to GCC (or maybe the linker?) will solve that, but that's the problem,
Sprow.

[toc] | [prev] | [next] | [standalone]

#5640

news@sprow.co.uk wrote:

> On Wednesday, 19 December 2018 17:58:43 UTC, Alexander Ausserstorfer
> wrote:
>> mail_applications -> armv3(all) -> pop3s-18th-dec.zip on a Risc PC 700
>> with StrongARM:
>>
>> | POP3S - E-Mail-fetcher with TLS for RISC OS
>> | Developer Version 16. April 2016
>> | GnuTLS version 3.5.8
>> |   000f2e2c : .@`å : e5604001 : STRB    R4,[R0,#-1]!
>> |   000f2e30 : .0Sâ : e2533001 : SUBS    R3,R3,#1
>> |   000f2e34 : ùÿÿ. : 1afffff9 : BNE     &000F2E20
>> |   000f2e38 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
>> |   000f2e3c : .ÿ/á : e12fff1e : BX      R14
>>
>> I have now idea why this is happen and what's going on. It seems to run
>> properly on my Raspberry Pi, though.
>
> This is the same problem (even the same instruction!) as I reported to
> you by email on 13-Aug-2018. BX R14 is an ARMv5 instruction, but the
> Risc PC is ARMv4 (if StrongARM) or ARMv3 (if ARM610/710), so you get
> an undefined instruction fault.
>
> I'm afraid I can't help figuring out which combination of switches to
> GCC (or maybe the linker?) will solve that, but that's the problem,

Thanks. I'm aware of that. I'm afraid that I cannot find your email
anymore.

Is the problem, that we (Ron, myself) compiled the code on the Iyonix PC
or on the Raspberry Pi? Because I cannot find any switches in the way I
compiled the code here to the time I compiled it on the Risc PC.
Nowadays, I have no Risc PC anymore to try it to compile it there. Does
!GCC recognize the machine it runs on and optimise automatically the
code to it?

A.

-- 
http://home.chiemgau-net.de/ausserstorfer/
Der Geist ist die Freiheit. (Frei.Wild)

[toc] | [prev] | [next] | [standalone]

#5641

In message <454f0a6857.beeb@-.->
          Ron <gettingchoppy@gmail.com> wrote:

>In message <420ffc6757.beeb@-.->
>          Ron <gettingchoppy@gmail.com> wrote:
>
>> Will rebuild crypt nettle with new stable then build libgnutls28 again.
>> 
>> Cheers RonM
>> 
>OK I started from scratch and built all the libraries that are pulled in
>by the libraries that are used in !POP3S
>They are all from the current stable/stretch repository.
>Should be at the same google drive link.
>
>It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
>often gets bigger.
>Another idea would be to try the RiscPC using gcc without the optimise
>flag.
>
>Let us know if compiling with those libraries improves things.
>Note that the gnutls28 is renewed/rebuilt also.

What is the reason for trying to build POP3S?  Is it simply to be able
to collect email from a server that requires SSL/TLS?  Because if
that's all, you could instead use the current build of AntiSpam.

AS doesn't /have/ to delete anything; it can be used simply as a
transport.  Recent builds support SSL/TLS using the beta AcornSSL
module available from ROOL.

There is a companion app to send email via SMTP using SSL/TLS.

All free of charge.

Dave

[toc] | [prev] | [next] | [standalone]

#5642

In message <974c846957.DaveMeUK@my.inbox.com>
          David Higton <dave@davehigton.me.uk> wrote:

> In message <454f0a6857.beeb@-.->
>           Ron <gettingchoppy@gmail.com> wrote:
> 
> >In message <420ffc6757.beeb@-.->
> >          Ron <gettingchoppy@gmail.com> wrote:
> >
> >> Will rebuild crypt nettle with new stable then build libgnutls28 again.
> >> 
> >> Cheers RonM
> >> 
> >OK I started from scratch and built all the libraries that are pulled in
> >by the libraries that are used in !POP3S
> >They are all from the current stable/stretch repository.
> >Should be at the same google drive link.
> >
> >It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
> >often gets bigger.
> >Another idea would be to try the RiscPC using gcc without the optimise
> >flag.
> >
> >Let us know if compiling with those libraries improves things.
> >Note that the gnutls28 is renewed/rebuilt also.
> 
> What is the reason for trying to build POP3S?  Is it simply to be able
> to collect email from a server that requires SSL/TLS?  Because if
> that's all, you could instead use the current build of AntiSpam.
> 
> AS doesn't /have/ to delete anything; it can be used simply as a
> transport.  Recent builds support SSL/TLS using the beta AcornSSL
> module available from ROOL.
> 
> There is a companion app to send email via SMTP using SSL/TLS.
> 
> All free of charge.
> 
> Dave
That may be, but if the GCCSDK is putting out wrongly we want to know
why if possible for future use.
Druck and Sprow have simplified the task at hand
A grep built with regex used like
grep -obUaP "\xe1\x2f\xff\x1e" /some/binary
reportedly works,and might help look through some libraries on the
cross compiler environment to see how widespread it is or point to
where the error is coming from.

I dont know if all the generic gcc arm switches are available in
GCCSDK gcc, there is genericly
-maps26 and -march=strongarm110 -mtune=strongarm110 type of thing
but the default of archv4 has been OK in the past.

Found my no 1 RiscPC SA last night but it has been 4-5 years,
and will take a bit of getting everything connected.

Ronald

[toc] | [prev] | [next] | [standalone]

#5643

In message <fc678a6957.beeb@-.->
          Ronald <gettingchoppy@gmail.com> wrote:

> grep -obUaP "\xe1\x2f\xff\x1e" /some/binary
> reportedly works,and might help look through some libraries on the
> cross compiler environment to see how widespread it is or point to
> where the error is coming from.
> 
> I dont know if all the generic gcc arm switches are available in
> GCCSDK gcc, there is genericly
> -maps26 and -march=strongarm110 -mtune=strongarm110 type of thing
the arch is already v4 so that would be -mcpu=strongarm110
> but the default of archv4 has been OK in the past.
> 
> Found my no 1 RiscPC SA last night but it has been 4-5 years,
> and will take a bit of getting everything connected.
> 
I think the requirement for the BX instruction to be present
would be E12FFF or to be sure not to be caught out by byte order
also FF2FE1
Neither returned hits in the static !RunImage, reducing down to
combinations of \xe1 and \x2f provided a few hits to show the grep
method does work.

I guess disassembling the !RunImage and text searching for BX
might also verify that there is no such instruction.
Puzzling then, where does the BX come from, the result of unixlib or
32bit library runtime? Getting my own RiscPC going will be an important
next step.

Ronald

[toc] | [prev] | [next] | [standalone]

#5644

On Friday, 21 December 2018 00:28:19 UTC, Ronald  wrote:
> In message <fc678a6957.beeb@-.->
>           Ronald <gettingchoppy@gmail.com> wrote:
> I think the requirement for the BX instruction to be present
> would be E12FFF or to be sure not to be caught out by byte order
> also FF2FE1
> Neither returned hits in the static !RunImage [...]
> Puzzling then, where does the BX come from

Then that search technique doesn't work. Dropping the !RunImage onto StrongEd and searching for "BX" gives 6 hits (of E12FFF1E),
Sprow. 

[toc] | [prev] | [next] | [standalone]

#5645

In message <748fdb89-18bb-46e6-bd2b-8327159e12f3@googlegroups.com>
          news@sprow.co.uk wrote:

> On Friday, 21 December 2018 00:28:19 UTC, Ronald  wrote:
> > In message <fc678a6957.beeb@-.->
> >           Ronald <gettingchoppy@gmail.com> wrote:
> > I think the requirement for the BX instruction to be present
> > would be E12FFF or to be sure not to be caught out by byte order
> > also FF2FE1
> > Neither returned hits in the static !RunImage [...]
> > Puzzling then, where does the BX come from
> 
> Then that search technique doesn't work. Dropping the !RunImage onto StrongEd and searching for "BX" gives 6 hits (of E12FFF1E),
> Sprow.

OK I will try that, text search on the binary and it works?
I have built libnettle using --disable-assembler and the !RunImage is
working on my SA RiscPC.
Alex, I have uploaded it and it looks like it will work until the
problem is found in the assembler routines.
Looking at nettle6 in the autobuilder, it could do with some work, It
builds common objects for both static and shared libs which means the
solibs objects aren't built with -fPIC.

Ronald

[toc] | [prev] | [next] | [standalone]

#5648

Ronald <gettingchoppy@gmail.com> wrote:

> In message <748fdb89-18bb-46e6-bd2b-8327159e12f3@googlegroups.com>
>          news@sprow.co.uk wrote:
>
>> On Friday, 21 December 2018 00:28:19 UTC, Ronald  wrote:
>> > In message <fc678a6957.beeb@-.->
>> >           Ronald <gettingchoppy@gmail.com> wrote:
>> > I think the requirement for the BX instruction to be present
>> > would be E12FFF or to be sure not to be caught out by byte order
>> > also FF2FE1
>> > Neither returned hits in the static !RunImage [...]
>> > Puzzling then, where does the BX come from
>>
>> Then that search technique doesn't work. Dropping the !RunImage onto
>> StrongEd and searching for "BX" gives 6 hits (of E12FFF1E), Sprow.
>
> OK I will try that, text search on the binary and it works?
> I have built libnettle using --disable-assembler and the !RunImage is
> working on my SA RiscPC.

The problem was the library libnettle? I never ported anything to RISC
OS. Just used what there is.

> Alex, I have uploaded it and it looks like it will work until the
> problem is found in the assembler routines.
> Looking at nettle6 in the autobuilder, it could do with some work, It
> builds common objects for both static and shared libs which means the
> solibs objects aren't built with -fPIC.

Many thanks, it is working now! Not the whole software, but the part of
TLS/SSL!!!

Hei konei ra,

Alex

-- 
http://home.chiemgau-net.de/ausserstorfer/
Beachte bitte auch die Rückseite dieses Schreibens!

[toc] | [prev] | [next] | [standalone]

#5650

In message <7960306a57.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:
<snip>

> The problem was the library libnettle? I never ported anything to RISC
> OS. Just used what there is.
> 
Yes Libnettle has arm assembler routines but they may only support
a minimum of archv5, so there is an option to use C routines that
are compiled to the gcc default of archv3. The gcc assembler 
obviously just assembles what it is told to without warnings.

The openSSL library has assembler routines that support archv4 
and the curl I compiled with this library works on the SA RiscPc,
one step further back than Nettle, like Nettle it has a no-asm option
to just use C routines for older hardware.


> > Alex, I have uploaded it and it looks like it will work until the
> > problem is found in the assembler routines.
> > Looking at nettle6 in the autobuilder, it could do with some work, It
> > builds common objects for both static and shared libs which means the
> > solibs objects aren't built with -fPIC.
> 
> Many thanks, it is working now! Not the whole software, but the part of
> TLS/SSL!!!
> 
I also uploaded the RiscPC(and older) safe libnettle.a so you can build
your own RunImage if you need to.

When I upgraded my fetchmail to openssl1.1.1 there were changes
required in the config but I found examples to help.
It stops ssl3 from being used. (no sslx support in openssl1.1.1)

Ronald

[toc] | [prev] | [next] | [standalone]

#5647

David Higton <dave@davehigton.me.uk> wrote:

> In message <454f0a6857.beeb@-.->
>           Ron <gettingchoppy@gmail.com> wrote:
>
>> In message <420ffc6757.beeb@-.->
>>           Ron <gettingchoppy@gmail.com> wrote:
>>
>>> Will rebuild crypt nettle with new stable then build libgnutls28 again.
>>>
>>> Cheers RonM
>>>
>> OK I started from scratch and built all the libraries that are pulled in
>> by the libraries that are used in !POP3S
>> They are all from the current stable/stretch repository.
>> Should be at the same google drive link.
>>
>> It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
>> often gets bigger.
>> Another idea would be to try the RiscPC using gcc without the optimise
>> flag.
>>
>> Let us know if compiling with those libraries improves things.
>> Note that the gnutls28 is renewed/rebuilt also.
>
> What is the reason for trying to build POP3S?  Is it simply to be able
> to collect email from a server that requires SSL/TLS?  Because if
> that's all, you could instead use the current build of AntiSpam.

I wasn't aware about it. Is it this here:

http://kasoft.com.au/Documentation/AnSpam.html

> AS doesn't /have/ to delete anything; it can be used simply as a
> transport.  Recent builds support SSL/TLS using the beta AcornSSL
> module available from ROOL.

I cannot find the AcornSSL module. Where can I find it? Is there a link
anywhere?

A.

-- 
http://home.chiemgau-net.de/ausserstorfer/
Der Geist ist die Freiheit. (Frei.Wild)

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.sys.acorn.programmer

csiph-web