Just catching up on some things... I have not had time to read recent posts in detail.

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

Keep in mind - DB's packet code has remained unchanged for many many years... for a reason. It works for the vast majority of people.

Also keep in mind my system - Darkrealms - Exchanges mail with at least 50, maybe 60+ downlinks, systems running Mystic, Synchronet, BBBS, etc etc... a multitude of different software. Darkrealms is a very popular mail-Hub, and DB powers all of the mail operation. No packet utilities, no custom workflows. Darkrealms also constantly exchanges mail with a NAB system - Ross Cassell.

So if someone is having problems receiving mail from a DB system, it is not
the DB system that is "buggy" nor does it need custom passwords or overrides specified in the BinkD configuration.

If I am not running ANY custom workarounds for the 60+ some-odd downlinks I exchange mail with, it stands to reason nobody else here should be either.

It should not be difficult for ANY system or BBS to accept packet passwords.

Just my two cents?

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On Sat May-28-2016 10:54, Nick Andre (1:229/426) wrote to All:

Just catching up on some things... I have not had time to read
recent posts in detail.

Can someone please clarify, in one or two sentences, what the
apparent problem is with passwords and where the supposed bug lines herein?

I sent two NETmails to you regarding this problem which just popped up a few months ago and tried to explain it as well as I could, keeping it short and to the point. Since I didn't hear from you, I naturally figured you must be very busy.


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

Re: I'm confused
By: Nick Andre to All on Sat May 28 2016 10:54 am

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

It appears that D'Bridge is adding passwords to outbound FTN packets when the sysop using D'Bridge has not explicity configured it to do so.

digital man

Synchronet "Real Fact" #63:
"Baja" (name of Synchronet PCMS compiler/languege) is pronounced "ba-ha". Norco, CA WX: 71.7°F, 62.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs

Nick,

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

As you know I'm the prime user of D'Bridge in nearly all its implementations and versions since ... ehr ... since ... ehr ... 1987? 1988? ... using it in an
IP-world even before you hit the scene and did all the good work you're doing.

Roger and I recall the old days when we prefered to work with Y2K-issues rather
than use the Y2K-ready version, the last-one Chris ever released and which was a shame.

For quite a long time I have been connecting with dozens of non-DB systems with
and without packet-password and never experienced an issue.

"Packet-password" has been implemented here from around 1994/1995 when I became
ZC.

Hope this helps,

\%/@rd

--- D'Bridge 3.99
* Origin: Many Glacier -- Protect - Preserve - Conserve (2:292/854)

Hello Nick,

On 28 May 16 10:54, Nick Andre wrote to All:

Just catching up on some things... I have not had time to read recent posts in detail.

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

Keep in mind - DB's packet code has remained unchanged for many many years... for a reason. It works for the vast majority of people.

Also keep in mind my system - Darkrealms - Exchanges mail with at
least 50, maybe 60+ downlinks, systems running Mystic, Synchronet,
BBBS, etc etc... a multitude of different software. Darkrealms is a
very popular mail-Hub, and DB powers all of the mail operation. No
packet utilities, no custom workflows. Darkrealms also constantly exchanges mail with a NAB system - Ross Cassell.

So if someone is having problems receiving mail from a DB system, it
is not the DB system that is "buggy" nor does it need custom passwords
or overrides specified in the BinkD configuration.

If I am not running ANY custom workarounds for the 60+ some-odd
downlinks I exchange mail with, it stands to reason nobody else here should be either.

It should not be difficult for ANY system or BBS to accept packet passwords.

Just my two cents?

Please post a message directly in Agoranet's test echo so I can see the original packet with no other systems in between. If there is no packet password included in your packet, then we'll have to search elsewhere. Although
if there is, then I can at least provide it to you for proof.

We have not been able to prove there is an apparant problem or bug with DB yet.
There has only been possible speculation in 3 different softwares.

However, it has been proven that some DB systems (if not all?) are sending a packet password while utilizing the "Session Password" setting in the Security section of DB. At the very least, that "Session Password" is being included in the original packet and noticed by the latest Mystic and Synchronet tossers.

This used to be ignored by sbbsecho due to sbbsecho's code being very old. Now there's a new version (v3) which doesn't ignore it any more. I'm unsure as to when Mystic started noticing this but there have been a few additions of Mystic
systems hubbing mail these days, so maybe it went unnoticed while Mystic's tosser code was still in heavy development (ie: not many wanted to be major hubs while the code was constantly changing - and now a couple have started their own networks).

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20160322
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

On 28 May 16 13:54:00, Roger Nelson said the following to Nick Andre:

I sent two NETmails to you regarding this problem which just popped up a fe months ago and tried to explain it as well as I could, keeping it short and the point. Since I didn't hear from you, I naturally figured you must be v busy.

I checked.

It is normal for the session password to included as the packet password.

It appears to of been designed this way since DB's inception.

The Packet Password screen is to override what is inserted.

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On 28 May 16 13:13:13, Rob Swindell said the following to Nick Andre:

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

It appears that D'Bridge is adding passwords to outbound FTN packets when t sysop using D'Bridge has not explicity configured it to do so.

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On 29 May 16 09:07:19, Nicholas Boel said the following to Nick Andre:

However, it has been proven that some DB systems (if not all?) are sending packet password while utilizing the "Session Password" setting in the Secur section of DB. At the very least, that "Session Password" is being included the original packet and noticed by the latest Mystic and Synchronet tossers

There is no bug, no problem. DB was designed to do this since the beginning.

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On Sun May-29-2016 10:57, Nick Andre (1:229/426) wrote to Roger Nelson:

On 28 May 16 13:54:00, Roger Nelson said the following to Nick
Andre:

I sent two NETmails to you regarding this problem which just popped
up a fe months ago and tried to explain it as well as I could,
keeping it short and the point. Since I didn't hear from you, I
naturally figured you must be very busy.

I checked.

Thank you.

It is normal for the session password to included as the packet
password.

Okay. That explains it.

It appears to of been designed this way since DB's inception.

Okay².

The Packet Password screen is to override what is inserted.

Got it. Thanks again.


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

Re: Re: I'm confused
By: Nick Andre to Rob Swindell on Sun May 29 2016 10:58 am

On 28 May 16 13:13:13, Rob Swindell said the following to Nick Andre:

Can someone please clarify, in one or two sentences, what the apparent problem is with passwords and where the supposed bug lines herein?

It appears that D'Bridge is adding passwords to outbound FTN packets when t sysop using D'Bridge has not explicity configured it to do so.

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

Oh, then you should point the DB sysops to the documentation that says that. There's been a lot of confusion and finger-pointing over this "non-bug". It's sounds like an incorrect "design" to me, but that's just my opinion.

digital man

Synchronet/BBS Terminology Definition #2:
ARS = Access Requirement Strings
Norco, CA WX: 68.9°F, 63.0% humidity, 13 mph SE wind, 0.00 inches rain/24hrs

Re: Re: I'm confused
By: Nick Andre to Rob Swindell on Sun May 29 2016 10:58:11

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

If I understand you correctly, if you do not configure a password, but have a session pw, that will be used as the packet PW, whether it is wanted or not. Should you configure a packet password that is different then the session PW, that is the one that would be used for the packet PW

Is that correct (sorry, my question mark comes up as É right now.)
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

On Sun May-29-2016 22:28, Joe Delahaye (1:249/303) wrote to Nick Andre:

Re: Re: I'm confused
By: Nick Andre to Rob Swindell on Sun May 29 2016 10:58:11

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

If I understand you correctly, if you do not configure a password,
but have a session pw, that will be used as the packet PW, whether
it is wanted or not. Should you configure a packet password that
is different then the session PW, that is the one that would be
used for the packet PW

Maybe others should ask Chris Irwin why he did it that way and why Nick left it
that way, but I'm positive both have good reasons. In fact, the more I think about it, the clearer it becomes.

Is that correct (sorry, my question mark comes up as É right now.)

As a suggestion, you should switch windows and then return to your editor window. That should make it go away and return your question mark. What did you expect for FREE? (-:0


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

Hello,

Have you received any NETmail from me recently?


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

On 29 May 16 22:28:04, Joe Delahaye said the following to Nick Andre:

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

If I understand you correctly, if you do not configure a password, but have session pw, that will be used as the packet PW, whether it is wanted or not Should you configure a packet password that is different then the session P that is the one that would be used for the packet PW

Yes.

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On 29 May 16 18:42:36, Rob Swindell said the following to Nick Andre:

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

Oh, then you should point the DB sysops to the documentation that says that There's been a lot of confusion and finger-pointing over this "non-bug". It sounds like an incorrect "design" to me, but that's just my opinion.

Perhaps, but this is the way it was designed since the beginning IIRC.

Nick

--- Renegade vY2Ka2
* Origin: www.darkrealms.ca (1:229/426)

On 29 May 16 18:42:36, Rob Swindell said the following to Nick Andre:

Oh, then you should point the DB sysops to the documentation that

says that

There's been a lot of confusion and finger-pointing over this

"non-bug". It

sounds like an incorrect "design" to me, but that's just my opinion.

Perhaps, but this is the way it was designed since the beginning IIRC.

So then what would happen when you send mail to a system you don't have a session password with? Answer: No packet password is presented. This is a good thing, IMO, and I like it that way.


Regards,

Roger

--- DB 3.99 + Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna (1:3828/7)

30 May 16 06:05, you wrote to Joe Delahaye:

Not a bug. DB is designed this way, and the Packet Password screen
overrides the password inserted.

If I understand you correctly, if you do not configure a password,
but have a session pw, that will be used as the packet PW, whether it
is wanted or not. Should you configure a packet password that is
different then the session PW, that is the one that would be used for
the packet PW

Maybe others should ask Chris Irwin why he did it that way and why
Nick left it that way, but I'm positive both have good reasons. In
fact, the more I think about it, the clearer it becomes.

my explanations should be helping in that understanding by now, too... frontdoor ran all up into it years ago from at least one particular mailer and had to adjust for it... with today's popular tossers having been ignoring the PKT passwords and now in recent months no longer ignoring them, the problem has
come to light yet again...

back then the problem was limited to FA (file attach) mailers... BSO mailers generally do not have this problem where the mailer checks the password in each
inbound PKT like a FA mailer might do... especially a dynamic mailer that packs
its own netmail from its netmail directory... BSO mailers need only check the initial session level password in the initial handshake traffic... DB being an intelligent dynamic FA mailer is doing what intelligent dynamic FA mailers do since it processes the PKTs as well as transferring them... to compare with frontdoor, FD only unpacked netmail from the PKTs and left the echomail alone but FD, like DB, also dynamically creates PKTs of netmail for destination systems... FD has only the session level password and the very first packet exchanged between the mailers contains the session level password... that first
packet is a stripped down PKT with the packet password being the session password else the two mailers won't know who they are talking to and whether the session is with the proper remote and not an impersonator... when the session is accepted, then the files on both sides are sent... those would be mail PKTs, including those PKTs dynamically packed by the mailer from its netmail directory, and tosser created mail bundles along with possibly other files and maybe accompanying TICs...

with today's prolific use of the binkp protocol, which uses a completely different manner of initial handshaking and confirming the remote is the system
it says it is, this problem can be excaberated by hybrid systems because the PKTs can contain a different from the session level password but valid PKT password because there is no initial empty PKT sent over binkp... binkleyterm and other BSO mailers do send an initial empty PKT with the addresses and session level password but that's the only PKT they create and process... all other PKTs, mail bundles and files are just transferred over the link...

)\/(ark

Always Mount a Scratch Monkey

... People who live in glass houses usually have faded sofas.
---
* Origin: (1:3634/12.73)

Re: I'm confused
By: Roger Nelson to Joe Delahaye on Mon May 30 2016 06:05:45

If I understand you correctly, if you do not configure a password,
but have a session pw, that will be used as the packet PW, whether
it is wanted or not. Should you configure a packet password that
is different then the session PW, that is the one that would be
used for the packet PW

Maybe others should ask Chris Irwin why he did it that way and why Nick left it
that way, but I'm positive both have good reasons. In fact, the more I think about it, the clearer it becomes.

Probably a mistake in logic. In my opinion it should never happen that way. You know what they say about opinions though :)

Is that correct (sorry, my question mark comes up as É right now.)

As a suggestion, you should switch windows and then return to your editor window. That should make it go away and return your question mark. What did you expect for FREE? (-:0

I have to reboot windows to fix it. I closed the telnet client, and restarted it, which often fixes it, but not this time.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: Re: I'm confused
By: Nick Andre to Joe Delahaye on Mon May 30 2016 08:43:17

If I understand you correctly, if you do not configure a password,
but have session pw, that will be used as the packet PW, whether it
is wanted or not Should you configure a packet password that is
different then the session P that is the one that would be used for
the packet PW

Yes.

OK, that clarifies. My thinking is that if you must have a packet PW, then it should be different then the Session PW.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: Re: I'm confused
By: Roger Nelson to Nick Andre on Mon May 30 2016 09:04:53

Perhaps, but this is the way it was designed since the beginning
IIRC.

So then what would happen when you send mail to a system you don't have a session password with? Answer: No packet password is presented. This is a good thing, IMO, and I like it that way.

IMO there should always be a Session PW. At least it gives some security
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Roger,

Have you received any NETmail from me recently?

Some days ago, yes.

\%/@rd

--- D'Bridge 3.99
* Origin: Many Glacier -- Protect - Preserve - Conserve (2:292/854)

Joe Delahaye wrote in a message to Roger Nelson:

I have to reboot windows to fix it. I closed the telnet client, and restarted it, which often fixes it, but not this time.

SHIFT-CTRL at the same time will put the keyboard out of french mode
and it will work correctly again.

Shawn
... Wedding rings: The world's smallest handcuffs.
---
* Origin: Tiny's Trailer (1:229/452.1)

Re: Re: I'm confused
By: Nick Andre to Rob Swindell on Mon May 30 2016 08:50 am

On 29 May 16 18:42:36, Rob Swindell said the following to Nick Andre:

Not a bug. DB is designed this way, and the Packet Password screen overrides the password inserted.

Oh, then you should point the DB sysops to the documentation that says that There's been a lot of confusion and finger-pointing over this "non-bug". It sounds like an incorrect "design" to me, but that's just my opinion.

Perhaps, but this is the way it was designed since the beginning IIRC.

And it's documented that way?

digital man

Synchronet/BBS Terminology Definition #11:
DCD = Data Carrier Detect
Norco, CA WX: 73.7°F, 56.0% humidity, 13 mph SE wind, 0.00 inches rain/24hrs

30 May 16 11:46, you wrote to Nick Andre:

If I understand you correctly, if you do not configure a password,
but have session pw, that will be used as the packet PW, whether it
is wanted or not Should you configure a packet password that is
different then the session P that is the one that would be used for
the packet PW

Yes.

OK, that clarifies. My thinking is that if you must have a packet PW,

then

it should be different then the Session PW.

it cannot always be like that... my previous postings abouot this over the years have explained why this is so...

)\/(ark

Always Mount a Scratch Monkey

... NBOS...The "No Balls OS", was Eunuchs.
---
* Origin: (1:3634/12.73)

Re: I'm confused
By: Shawn Highfield to Joe Delahaye on Mon May 30 2016 14:46:40

I have to reboot windows to fix it. I closed the telnet client, and
restarted it, which often fixes it, but not this time.

SHIFT-CTRL at the same time will put the keyboard out of french mode
and it will work correctly again.

I'll try to remember that <G> I'd like to know how it gets into that mode though
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: I'm confused
By: mark lewis to Joe Delahaye on Mon May 30 2016 18:08:08

OK, that clarifies. My thinking is that if you must have a packet
PW, then it should be different then the Session PW.

it cannot always be like that... my previous postings abouot this over the years have explained why this is so...

Why not? There is absolutely no reason why it should not be so. It seems that the original programmer of DB decided to force a packet PW, and others decided to ignore it <G>
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

On Tue May-31-2016 10:49, Joe Delahaye (1:249/303) wrote to mark lewis:

Re: I'm confused
By: mark lewis to Joe Delahaye on Mon May 30 2016 18:08:08

OK, that clarifies. My thinking is that if you must have a packet
PW, then it should be different then the Session PW.

it cannot always be like that... my previous postings abouot this
over the years have explained why this is so...

Why not? There is absolutely no reason why it should not be so.
It seems that the original programmer of DB decided to force a
packet PW, and others decided to ignore it <G>

Just as others may decide to ignore your comment. (-:

...If confusion was consumption, you'd be consumed.


Regards,

Roger
--- timEd/386 1.10.y2k+ Windows 10
* Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)

Joe Delahaye wrote in a message to Shawn Highfield:

SHIFT-CTRL at the same time will put the keyboard out of french mode
and it will work correctly again.

I'll try to remember that <G> I'd like to know how it gets into
that mode though

The same way. :) You are typing so fast you hit shift ctrl. ;)

Shawn
... Few things are as painful as the truth realised too late.
---
* Origin: Tiny's Trailer (1:229/452.1)

31 May 16 10:49, you wrote to me:

OK, that clarifies. My thinking is that if you must have a packet
PW, then it should be different then the Session PW.

it cannot always be like that... my previous postings abouot this
over the years have explained why this is so...

Why not? There is absolutely no reason why it should not be so.

i've already written about this... many times over the years and once again in the last few days... are you missing mail???

It seems that the original programmer of DB decided to force a packet
PW, and others decided to ignore it <G>

to a point, this is true on both accounts...

)\/(ark

Always Mount a Scratch Monkey

... Infants have less fun in infancy than adults do in adultery!!!
---
* Origin: (1:3634/12.73)

Re: I'm confused
By: Roger Nelson to Joe Delahaye on Tue May 31 2016 11:30:50

it cannot always be like that... my previous postings abouot this
over the years have explained why this is so...

Why not? There is absolutely no reason why it should not be so.
It seems that the original programmer of DB decided to force a
packet PW, and others decided to ignore it <G>

Just as others may decide to ignore your comment. (-:

They may do so of course. Does not obfuscate the fact that others did indeed ignore it, depending on configurations
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: I'm confused
By: Shawn Highfield to Joe Delahaye on Tue May 31 2016 13:24:26

SHIFT-CTRL at the same time will put the keyboard out of french mode
and it will work correctly again.

I'll try to remember that <G> I'd like to know how it gets into
that mode though

The same way. :) You are typing so fast you hit shift ctrl. ;)

I do touch type, but I will have to try that and see what happens <G>

ÉÉÉÉéé/? Seems like you have to hit it 3 times to get back to normal <G>
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: I'm confused
By: mark lewis to Joe Delahaye on Tue May 31 2016 13:00:42

it cannot always be like that... my previous postings abouot this
over the years have explained why this is so...

Why not? There is absolutely no reason why it should not be so.

i've already written about this... many times over the years and once again in the last few days... are you missing mail???

You may have, and I may have missed it in that case. Explain to me why it cannot always be like that. It is simply code, and it can be written to do what you want it to do.

It seems that the original programmer of DB decided to force a
packet PW, and others decided to ignore it <G>

to a point, this is true on both accounts...

Yes
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Joe Delahaye wrote in a message to Shawn Highfield:

EEEEee/? Seems like you have to hit it 3 times to get back to
normal <G>

Well now you can do it without rebooting anyway. :) hahaha I don't
understand why it works that way.

Shawn
... I don't make jokes. I just watch the government and report the facts.
---
* Origin: Tiny's Trailer (1:229/452.1)

Re: I'm confused
By: Shawn Highfield to Joe Delahaye on Tue May 31 2016 19:18:16

EEEEee/? Seems like you have to hit it 3 times to get back to
normal <G>

Well now you can do it without rebooting anyway. :) hahaha I don't understand why it works that way.

Hopefully it will work that way next time <G> My buddy had a problem in Skype yesterday, and that trick did not fix it. Perhaps a reboot of Skype will.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

31 May 16 16:41, you wrote to me:

i've already written about this... many times over the years and once
again in the last few days... are you missing mail???

You may have, and I may have missed it in that case. Explain to me
why it cannot always be like that.

see (routed) netmail coming your way... same subject line...

)\/(ark

Always Mount a Scratch Monkey

... Sounds like you've been snacking on some of the local mushrooms!
---
* Origin: (1:3634/12.73)

Re: I'm confused
By: mark lewis to Joe Delahaye on Wed Jun 01 2016 11:54:44

You may have, and I may have missed it in that case. Explain to me
why it cannot always be like that.

see (routed) netmail coming your way... same subject line...

Nothing yet, but you could have sent direct ya know <G>
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Joe Delahaye wrote in a message to Shawn Highfield:

Hopefully it will work that way next time <G> My buddy had a
problem in Skype yesterday, and that trick did not fix it. Perhaps
a reboot of Skype will.

Ask him to click outside of skype to the windows desktop, then hit the
magic keys and it /should/ work. ;)

Shawn

... A cult is a religion with no political power.
---
* Origin: Tiny's Trailer (1:229/452.1)

01 Jun 16 13:55, you wrote to me:

You may have, and I may have missed it in that case. Explain to me
why it cannot always be like that.

see (routed) netmail coming your way... same subject line...

Nothing yet, but you could have sent direct ya know <G>

maybe but this is a point system and some systems reject point connections if there's a session level password between the boss and the destination... i don't remember if we have a direct connection, password protected or not...

)\/(ark

Always Mount a Scratch Monkey

... "Even the best of friends cannot attend each other's funeral." ─ Albran
---
* Origin: (1:3634/12.73)

Re: I'm confused
By: Shawn Highfield to Joe Delahaye on Wed Jun 01 2016 15:35:58

Ask him to click outside of skype to the windows desktop, then hit the magic keys and it /should/ work. ;)

OK, will do that, thankjs.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: I'm confused
By: mark lewis to Joe Delahaye on Wed Jun 01 2016 16:38:00

see (routed) netmail coming your way... same subject line...

Nothing yet, but you could have sent direct ya know <G>

maybe but this is a point system and some systems reject point connections if there's a session level password between the boss and the destination... i don't remember if we have a direct connection, password protected or not...

Still nothing here. No bad mail either.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)