[nos-bbs] case sensitivity of MID/BID - discussion needed

[Boudewijn (Bob) Tenty]

Maybe some case-sensitive examples are available as I only could find an 
example with completely
changed bids. This was due to a bug in linBPQ version 6.0.9.31

Bob VE3TOK


    16169URGENT - Duplicate Bulls in linbpq version 6.0.9.31 and BPQMal
    1.4.62.2-6

/Expand Messages/

  *
    John Wiseman
    Feb 6 4:58 AM

    A version of LinBPQ which can in some circumstances create a new BID
    for an incoming message was available on dropbox from around Jan
    21^st to Feb 3^rd The affected version is 6.0.9.31. If you are
    running this version, please update as soon as possible.

    The same bug could be in versions of BPQMail between 1.4.62.2 and
    1.4.62.6.

    My apologies for any inconvenience caused.

    Just for the record, this isn’t the same issue reported where the
    case of BIDS has been changed. In this case a new BID is generated
    from  the receiving station’s  Message Number and Call.

    73, John

  *





On 15-02-08 12:53 PM, Maiko Langelaar wrote:
>
> Recently I received an email from a JNOS user, and he brings up a very
> interesting point. Some of you may have already read up about this on
> the BPQ32 Yahoo group.
>
> Why am I bringing this up ? Apparently the issue cause multiple copies
> of the same message to appear at people's systems. I suppose one could
> look at the expression, 'better 2 then none', but anyways ...
>
>> I'm no expert on BBSs, but it seems to me the root problem is that BPQ
>> is making case-sensitive comparisons of MIDs/BIDs and when the other
>> major BBSs (JNOS, TNOS and apparently FBB) evidently don't care about
>> case.
>
> Putting in my 2 cents worth, JNOS (and TNOS too) may very well be sending
> out lower case bids for non FBB forwarding session. Other then that, JNOS
> and TNOS both use uppercase for FBB proposals (automatically uppercase
> any bid values). As for comparison, JNOS and TNOS use strcasecmp, so the
> case is actually ignored when 'we' do it. We don't care about case.
>
>> After all, if you make the change to always force upper case, then BPQ
>> still has a problem if an originating BBS uses lower case.  So either
>> everyone needs to be either case-sensitive or case-insensitive. Right?
>
> I don't want this to be a BPQ vs 'the rest of them' issue.
>
> From my perspective, I can try and ensure that NOS is 'consistent' with
> keeping it uppercase (for starters). But the logistics of asking ALL of
> the NOS users out there to patch just this one issue is raised. We could
> probably eliminate the majority of these issues by telling people to just
> stop using mbox fbb 0 (non fbb forward modes), not sure how well that 
> will
> be received by sysops. Perhaps that will force them to understand why
> they are not able to get mbox fbb 1 or higher to work properly ?
>
> Even if the consensus is to agree to case sensitivity, we still need to
> get the systems out there updated. What a mess this might be.
>
> So, let's talk about it ... the BPQ guys are, so perhaps we should too :)
>
> Maybe after this discussion, then we could get the 3 or 4 maintainers
> or authors to have an internal email talk about the results ? Or am I
> being naive (even after all these years of doing this) ???
>
> Maiko
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20150208/7a4b8f5c/attachment.html>