I put the copy of my magiterm for mac os in a zip file to see if it works
for others.

It will need macOS 13.6+ but should work on both intel and Apple Silicon.

I'm mostly interested if the keychain stuff works...

So if you have a mac, please help test if :D

Andrew


--- Talisman v0.53-dev (FreeBSD/amd64)
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

I put the copy of my magiterm for mac os in a zip file to see if it works for others.

It will need macOS 13.6+ but should work on both intel and Apple Silicon.

I'm mostly interested if the keychain stuff works...

So if you have a mac, please help test if :D

Andrew

Probably help if I include a url

https://talismanbbs.com/downloads/MagiTerm/experimental/


Andrew


--- Noddy git-4716e54
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

I put the copy of my magiterm for mac os in a zip file to see if it works for others.

It will need macOS 13.6+ but should work on both intel and Apple Silicon.

I'm mostly interested if the keychain stuff works...

It worked as expected here (Sonoma 14.2.1) -

I downloaded the zip file and double-clicked MagiTerm to run it.

Got a pop-up window:

"MagiTerm" can't be opened
because Apple cannot check it
for malicious software.

This software needs to be updated.
Contact the developer for more information.

with "Show in Finder" button and "Cancel" button.

In System Settings -> Privacy and Security -> "MagiTerm" was blocked from use because it is not from an identified developer.

Clicked "Open Anyway" and entered my password

Pop-up second time:

"MagiTerm" can't be opened
because Apple cannot check it
for malicious software.

This time there's an "Open" button.

From this point, MagiTerm runs normally like any other application.

I added an entry to the dialing directory with a username and password, exited the program and reopened the program and it appears it was saved OK, I saw no messages related to the keychain. (I didn't actually connect to a BBS using the saved username/password because I always login manually on telnet so I don't usually save login details in the dialing directory and I gotta look up an SSH port to connect to or whatever to use it)


Chris/akacastor

--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)

I added an entry to the dialing directory with a username and
password, exited the program and reopened the program and it appears
it was saved OK, I saw no messages related to the keychain. (I didn't actually connect to a BBS using the saved username/password because I
always login manually on telnet so I don't usually save login details
in the dialing directory and I gotta look up an SSH port to connect to
or whatever to use it)

Oh great, thanks for testing it, just to confirm the ones with saved
passwords have little yellow asterixes near the start of the entry in the
list?

This is good. Now i just need to figure out what's going on with the
keychain here >.< lol

Thanks,

Andrew


--- Talisman v0.53-dev (FreeBSD/amd64)
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

Oh great, thanks for testing it, just to confirm the ones with saved passwords have little yellow asterixes near the start of the entry in the list?

Yes they show the yellow asterisk beside the 'S'.

This is good. Now i just need to figure out what's going on with the keychain here >.< lol

I put an airtag on my keychain in case I misplace it! (hey it's almost 1am here, this is the kind of response I produce when I have nothing useful to add) :)


Chris/akacastor

--- Maximus 3.01
* Origin: Another Millennium - Canada - another.tel (21:1/162)

Yes they show the yellow asterisk beside the 'S'.

Thanks!

I put an airtag on my keychain in case I misplace it! (hey it's
almost 1am here, this is the kind of response I produce when I have
nothing useful to add) :)

Hehe

Andrew


--- Talisman v0.53-dev (FreeBSD/amd64)
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

Re: MagiTerm MacOS
By: apam to All on Wed Mar 27 2024 03:57 pm

Howdy,

It will need macOS 13.6+ but should work on both intel and Apple Silicon. I'm mostly interested if the keychain stuff works...
So if you have a mac, please help test if :D

So I downloaded and ran (I'm on an M1) - and yes I had to right click, open the first time and confirm that I was running an unsigned app.

I've obviously played with Magiterm before - since it found my existing BBS list - but when I updated my BBS to its internal 10.x.x.x address and port 123, and selecting it to connect, Magiterm disappeared.

(If I changed the port to 23, it connected to my ANSItex environment OK, so it seems it didnt like port 123 for some reason...?)

Also, if I used the hostname that resolved to an IPv6 address only, it just said "An error occured!".


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

(If I changed the port to 23, it connected to my ANSItex environment
OK, so it seems it didnt like port 123 for some reason...?)

That's odd.

What listens on port 123? Is it something I can connect to? Thinking
maybe it's some telnet negotiation that is confusing it perhaps?

Also, if I used the hostname that resolved to an IPv6 address only, it
just said "An error occured!".

Hmm, I probably haven't added IPv6 support. I tend to forget what I've
done and what I haven't done on various projects.

Andrew


--- Talisman v0.53-dev (FreeBSD/amd64)
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

Re: MagiTerm MacOS
By: apam to deon on Thu Mar 28 2024 10:58 am

That's odd.

What listens on port 123? Is it something I can connect to? Thinking
maybe it's some telnet negotiation that is confusing it perhaps?

Synchronet.

I'm not sure that it actually sends out a TCP connection (might do, but as soon as I press Enter on the entry, magiterm disappears.)

Anyway, port 23 (also Synchronet - and the same one) answers fine - it just launches my ANSItex shell (which would have the same telnet negotiations going on).

===

I just deleted Magiterm (actually accidently) - so reinstalled it, and it worked (I didnt change the phone book). I then edited the phone book, changed nothing, and saved it, and it dissappeared when entering to connect.

When I re-opened it, it worked - then I did the same edit, no change, save thing and it disappeared (when entering to connect). Not sure if that helps?

===

OK, played some more and now it doesnt open at all - regardless of whether I edit it. I even moved the selection line (down and back) which worked, but now consistently doesnt.

It only appears to affect the first entry in the phone book, if I change another entry to ip address only, and port 123, it appears to work consitently.

So perhaps some buffer initialisation, or off by 1 thing?




...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

OK, played some more and now it doesnt open at all - regardless of
whether I edit it. I even moved the selection line (down and back)
which worked, but now consistently doesnt.

It only appears to affect the first entry in the phone book, if I
change another entry to ip address only, and port 123, it appears to
work consitently.

So perhaps some buffer initialisation, or off by 1 thing?

Maybe, I can't seem to reproduce it though. your dialing directory lives
in

/Users/[username]/Library/Application Support/Magicka/MagiTerm/

(as do the known_hosts file and prefs.ini)

Could you try moving the dialdirectory.ini out and starting magiterm
again (it won't flush out your key chain, so you can either make sure you
use the same names or use the keychain browser).

If it's something corrupted, and is now consitently corrupted, I'm
thinking there might be a clue in the dialdirectory.ini.

Andrew


--- Talisman v0.53-dev (FreeBSD/amd64)
* Origin: Smuggler's Cove - scove.talismanbbs.com:2323 (21:1/182)

Re: MagiTerm MacOS
By: apam to deon on Thu Mar 28 2024 01:24 pm

Howdy,

Maybe, I can't seem to reproduce it though. your dialing directory lives
in

/Users/[username]/Library/Application Support/Magicka/MagiTerm/

So I had a look at the dialdirectiory.ini and it looks OK (no signs of corruption).

I moved it out and created a new one - with just the 1 entry and cant produce it.

I moved it back, and still cant produce it. Truely odd. I'll let you know if something changes and I can trigger it...


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)