Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
87 user(s) are online (55 user(s) are browsing Forums)

Members: 2
Guests: 85

Georg, jarokuczi, more...

Headlines

Forum Index


Board index » All Posts (pjs)




Re: Is a Google account accessible using Odyssey beta 7?
Not too shy to talk
Not too shy to talk


@Raziel

;D

FWIW, I just tried logging again now... went in via
calendar.google.com link and was able to see my account's
appointments, gmail, etc.

What we really need to do is pool our $$$ and rent a
server for just us lowly Amigans to have our own accounts
with contacts, calendars, etc. with no big brother lurking.

An Idea!

;)

PJS

Go to top


Re: AOrganiser won't finish syncing
Not too shy to talk
Not too shy to talk


Hi Paul,

Dunno if maybe goggles screwed something up... ever
"improving" things.

In any case, I was still able to log-in and use AOrganizer
all the time with my goggles account.

Maybe you should first try logging into your goggles
accounts and making sure they all work. ....before trying
to sync?

Maybe setting up some spoofing for them will improve
things?

Unfortunately, websurfing on Amigas is *not* for sissies!

;D

PJS

Go to top


Re: Is a Google account accessible using Odyssey beta 7?
Not too shy to talk
Not too shy to talk


Hi Paul

FWIW, I use AOrganizer regularly with Goggles and it's
generally been very reliable.

I'll have to test to see if I can still log in.

Up till fairly recently, I was able to use gmail with
IBrowse, but they improved that out too.

Yay Shit Web Coders!

Stay tuned,

PJS

Go to top


Re: Newer SSL certs on Timberwolf?
Not too shy to talk
Not too shy to talk


Hey guys,

While I suspect there has to be a way to replace the certs,
I wonder if the problem has more one to do with the various
encryption algorthyms themselves...

It looks like the last builds of TW were in 2012 and we've
gone through a lot of hacks/updates to SSL, etc. since
then.

Like with Oddity, even if the old TW could be recompiled
with new SSL (etc) components, it might open up a few
things?

But the only people that can compile it are the Friedens
AFAIK. I thought ssolie looked at trying to get it to
compile, but ran out of time/energy. It's not an
insignificant challenge.

:/

PJS

Go to top


Re: Getting into ZIP JAR files?
Not too shy to talk
Not too shy to talk



*LOL*

That's pretty funny.... So I tried the 14 year old unzip
CLI utility and it worked!

;)

Soooo.... bug in the XAD driver then? hmmm....

At least there's a way to make it work.

Thanks,

PJS

Go to top


Re: Getting into ZIP JAR files?
Not too shy to talk
Not too shy to talk


@nbache

Hi Niels!

Most often I see that these files already have .zip
suffices on them. So it doesn't seem like that's the
issue.

Like I said it gets opened by Unarc, but everything
is "empty".

Given that our latest unzip appears to be from 2006 (!!),
I didn't think to try it. hmmmmm...

Thanks,

PJS


Go to top


Getting into ZIP JAR files?
Not too shy to talk
Not too shy to talk


Hi guys,

I'm encountering more and more of this new version of "zip" files...

They are listed in the WB as "Rp9" files, Unarc opens them and shows
their contents, but all the files are listed as 0 bytes
("100% compression"! ;) ).

I understand they are actually a ZIP subset called JAR files...

https://en.wikipedia.org/wiki/.jar

That page claims "standard decompression software" or some app called "jar"
should decompress the files. Not here! :/

Do we need a new XAD driver?

Anyone have any experience with these? Any ideas how to get through this
new layer of peecee obfuscation?

Thanks in advance!

PJS


Go to top


Re: Basilisk anyone?
Not too shy to talk
Not too shy to talk


Hi LiveForIt!

I don't know if it helps any, but I'm not suggesting you
get "into" a SANA-2 driver, but just bring one up...

No different than if you were calling a dedicated physical
net port or like how the classic emulation used to use the
A2065 card.

The tunnelling solution can be priovided externally and
has already been done with the VLink SANA driver:

http://aminet.net/package/comm/tcp/vlink

It worked great with MiamiDx 20+ years ago and I asked
Olaf Barthel specifically about it and Roadshow and he
said it should continue to work as such.

Please let us know what you think!

Thanks,

PJS


Go to top


Basilisk anyone?
Not too shy to talk
Not too shy to talk


Hi all,

I came across this link recently with a mess of old Mac software, a lot
that's been tested on Amiga (& derivative) emulators - something new to
play with?

https://macintoshgarden.org/all

So I thought I'd take another look at our Basilisk port. It runs, but
there are problems and I wondered if any work had been done to it? Any
interest?

I've emailed with Olaf and he suggested the old VLink virtual SANA driver
should work with RS to allow Basilisk net access (like used to work GREAT
with Shapeshifter). But it appears Basilisk's net support is inhibited.
Could this be reopened?

I'm also seeing that Basilisk's file access to the Amiga side is broken. If
I try to access ramdisk, I just get crashes. Worth posting?

Anyone know anything more about Basilisk or is it just "dead Jim"?

Thanks,

Go to top


Re: Amigans.net 2020 updates
Not too shy to talk
Not too shy to talk


@walkero

I'm also posting from IBrowse 2.5.3! Amigans looks great!

Wonderful job! THANKS

PJS


Go to top


Re: atheros wlan device is working
Not too shy to talk
Not too shy to talk


@ncafferkey

Thanks for sending out the latest update!

I understand adding some pop-up GUI would require a fair
bit of coding.

Maybe an easier stopgap would be to make WirelessManager
able to process a Break message (ctrl-c) or to give it an
ARexx port with a "QUIT" command?

Obviously, an ARexx port would provide a whole avenue for
on-the-fly reconfiguration, status reporting, etc.

Thanks again,

PJS

Go to top


Re: SSH client for AmigaOS with builtin terminal emulation
Not too shy to talk
Not too shy to talk


@salass00

Thanks for posting the update! I tried it and it worked
great...

I copied from SSHTerm, pasted straight back in and I pasted
into Notepad and copied/pasted that back into SSHTerm and
it all worked great!

Looks like you've got that issue resolved.

Thanks again,

PJS

Go to top


Re: Odyssey 1.23 progress
Not too shy to talk
Not too shy to talk



Hi kas1e,

Yeah, somehow I doubted it was going to be THAT easy, but
I had hope... ;D

I only mentioned Curl since I figured it might be involved
in some of all the transport security updating that has
been going on since the last update (heartbleed, etc etc
etc).

The same goes for OpenSSL... There are so many secure sites
(banks, etc) that kick out errors or just refuse to connect
now and I've wondered if security updates might help that.

Thanks again,

PJS

Go to top


Re: SSH client for AmigaOS with builtin terminal emulation
Not too shy to talk
Not too shy to talk


Hi Frederik,

Congrats on the progress with SSHTerm!

I got a break and installed the new v1.4 version and it seems to be
working quickly. :D

I tried some of the command lines from before. All of these worked as
expected, although some still complained (in spite of working)...

---

SSHTerm shell.xmission.com PORT 443 <shell un> KEYFILE devs:ssh/id_rsa
[ ASKED ME FOR MY pw AND WORKED

SSHTerm shell.xmission.com PORT 443 <shell un> PASSWORD <ssh pw> KEYFILE devs:ssh/id_rsa
[ IT CONNECTED & WORKED, BUT PRINTED THIS OUT:
[ id_rsa
[ Failed to connect to ssh-agent

SSHTerm shell.xmission.com <shell un> PASSWORD <ssh pw> KEYFILE devs:ssh/id_rsa
[ WITHOUT THE PORT, IT CONNECTED & WORKED, BUT STILL PRINTED THIS OUT:
[ Failed to connect to ssh-agent

SSHTerm shell.xmission.com <shell un> KEYFILE devs:ssh/id_rsa
[ JUST LIKE ABOVE, IT ASKEDD FOR MY pw, CONNECTED & WORKED, BUT STILL PRINTED THIS OUT:
[ Failed to connect to ssh-agent

SSHTerm shell.xmission.com <shell un>
[ ASKED ME FOR MY shell pw AND WORKED

SSHTerm shell.xmission.com <shell un> PASSWORD <shell pw>
[ WORKED

---

I also tried copying and pasting to/from SSHTerm. It looks like going
from SSHTerm->Notepad is working fine. Unfortunately, going the other
way (Notepad->SSHTerm) appears to still be missing or stripping linefeeds
and/or carriage returns.

Is this just platform issues with the handling of CR's, LF's and/or
CR-LF's? Should SSHTerm maybe have some options for translating those
between platforms?

Next, I need to figure out what to do with the window pallette... There
must be a way it can be set in the session. hmmm...

Thanks again!

PJS

Go to top


Re: Odyssey 1.23 progress
Not too shy to talk
Not too shy to talk


@kas1e

Thanks again for working on this.

Any ideas how hard it would be to update the OpenSSL or the
Curl being used? Could it be as simple as a rebuild or
more involved?

Thanks,

PJS


Go to top


Re: Odyssey 1.23: AOS4 source code on GitHub
Not too shy to talk
Not too shy to talk


@kas1e

Thanks for putting the time into pushing the boulder
forward on this one. Here's hoping simplifying building
might result in a bit more progress.

Thanks again,

PJS

Go to top


Re: SSH client for AmigaOS with builtin terminal emulation
Not too shy to talk
Not too shy to talk


Hi again Salas00,

I'm sorry, I just don't know what to tell you about the types of
authentication being used...

I barely figured out how to get it working with ssolie's OpenSSH
(the docs are fairly incomplete/innacurate), but it's since been
working on all my Amigas and even from my Mac with the "id_rsa"
file copied over to it.

So I just don't what else to tell you about the technical details.

OK, I've noticed a few other things running SSHTerm on my Amigas...

First, I have encountered this problem sporadically and I haven't
been able to trace back what sets it off..

If I select text in the SSHTerm window (in an Alpine session) and
paste it into Notepad, I am seeing that most of the spaces (after
the first one) are getting stripped out of the resulting text.

Next, if I correct the missing spaces in Notepad, go back into
SSHTerm (and Alpine) and paste the text back in, then I'm seeing
the LF's or CR's (I don't remember which we use) get stripped out
in the resulting text.

Hope this helps.

Thanks again,

PJS

Go to top


Re: SSH client for AmigaOS with builtin terminal emulation
Not too shy to talk
Not too shy to talk


Hi salas00 !

Congratulations on your release of SSHTerm! Fantastic and very much
appreciated.

I installed it and have been testing it with my shell account on
XMission. Normally, I log into that account using openssh on my
Amigas and have managed to force the server to use the console's
ANSI terminal support (most of the time).

Once I got a command line that worked, I was able to connect to
XMission and it seemed to work great. Even on my little ole SAM440
on wifi it didn't seem terribly slow or cause any CPU load.
Resizing a full shell window was the only time things crawled (maybe
it shouldn't try to do constant redraw?).

I also found that your terminal emulation was working well! :D
I've been finding more and more shell apps that simply ignore the
TERM settings which just kill Amiga ANSI use.

But I had a few challenges with getting SSHTerm to connect to start
with...

First, it doesn't work with openssh and its keyfile. As per the
openssh docs, my "id_rsa" is in DEVS:ssh/. Any of these command
lines with SSHTerm never worked:

------

SSHTerm/SSHTerm shell.xmission.com <un> devs:ssh/id_rsa.pub
<< window open/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com <un> devs:ssh/id_rsa
<< window open/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com USER <un> KEYFILE devs:ssh/id_rsa
<< window open/asked me for pw/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com PORT 443 USER <un> KEYFILE devs:ssh/id_rsa
<< window open/asked me for pw/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com USER <un> PASSWORD <ssh pw> KEYFILE devs:ssh/id_rsa
<< window open/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com PORT 443 USER <un> PASSWORD <ssh pw> KEYFILE devs:ssh/id_rsa
<< window open/closed >>
Authentication failed

SSHTerm/SSHTerm shell.xmission.com PORT 443 USER <un> PASSWORD <ssh pw>
<< window open/closed >>
Authentication failed
------

Finally, I gave up on trying to use my SSH keyfile and I tried
connecting with the shell account's "normal" password...

------

SSHTerm/SSHTerm shell.xmission.com PORT 443 USER <un>
<< asked me for my shell pw and IT WORKED!! :D >>

SSHTerm/SSHTerm shell.xmission.com 443 <un>
<< window open/closed >>
Authentication failed

SSHTerm shell.xmission.com PORT 443 USER <un> PASSWORD <shell acct pw>
<< IT WORKED >>

SSHTerm shell.xmission.com PORT 443 <un> <shell acct pw>
<< IT WORKED >>

SSHTerm shell.xmission.com 443 <un> <shell acct pw>
wrong number of arguments

SSHTerm shell.xmission.com <un> <shell acct pw>
<< IT WORKED >>

------

So it seems like SSHTerm is also having problems parsing the command line
for arguments... Even if the exact same combination of arguments fails
if you don't have the keywords (PORT, USER, etc). It seems to really need
the "PORT" in there if you're going to set a port number.

Finally, wishes... I hope you might consider an option for letting the user
set the window initial size, colors, sound.

In any case, Thanks again! It's a wonderful achievement. I'll start
using it on all my machines and see how it gets along.

THANKS!

PJS

Go to top


Re: QFtpServer - Ftp/ftps server for Qt4
Not too shy to talk
Not too shy to talk


hmmm....

I tried every executable I could find in the distrib and
none worked... No crashes, just not running.

In the case of the QFtpServer/QFtpServer/QFtpServer (yes,
that buried), it complained about missing this file:

libQFtpServerLib.so

...and then DOS kicked back a console window saying the
file was "not executable".

Yes, there's such an .so in the QFtpServerLib dir, but are
we supposed to hand assemble a workable directory tree for
this thing to run?

PJS

Go to top


Re: Arexx question
Not too shy to talk
Not too shy to talk


Hi DaveyW,

While I know there are shorterhand ways of doing this, the
longhand way always worked for me...

/* Ask User Choice & Print Out
*/
TitleBarTxt = 'Test Requester'
BodyTxt = 'Pick something!'
ButtonsTxt = '"Yes" "Umm" "No"'
ReqType = 'INFO'
cline = 'c:requestchoice "' || (TitleBarTxt) || '" "' || BodyTxt || '" ' || (ButtonsTxt) || ' TYPE ' || (ReqType) || ' TO T:response.txt'
address command cline
MyReturnCode = RC
if exists('T:response.txt') then
if open(ReqF,'T:response.txt','r') then do
pick = strip(readln(ReqF),'B','"')
bs = close(ReqF)
address command 'c:delete T:response.txt'
say 'response >' pick '<'
end
else
say 'Couldn''t open Requester output file'

Fundamentally, you've have to read the output file from the
Req... command.

Good luck,

PJS

Go to top



TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 17 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project