johnsonhammond1 | 27 Apr 2013 19:45
Favicon

Biggest Fake Conference in Computer Science

Biggest Fake Conference in Computer Science

We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.

We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware

Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 

We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
(Continue reading)

Hannes Tschofenig | 16 Mar 2013 16:25
Picon

HOTP Errata & Implementations

Hi all, 

in 2011 we published the TOTP with RFC 6238
http://tools.ietf.org/html/rfc6238

TOTP normatively references HOTP (RFC 4226, see http://www.ietf.org/rfc/rfc4226.txt). 

It turns out that HOTP has a few errata pending (see
http://www.rfc-editor.org/errata_search.php?rfc=4226&rec_status=2&presentation=records). 

Is anyone in this group interested to discuss these errata issues with me?

It would also be interesting to hear what people had implemented. 

Please drop me a mail. 

Ciao
Hannes

Anders Rundgren | 2 Jan 2013 21:24
Picon

2013: KEYPROV II

http://webpki.org/papers/PKI/certenroll-features.pdf

It is currently in beta state for Android.  The specs are here:

   http://webpki.org/auth-token-4-the-cloud.html

Anders

RFC Errata System | 27 Nov 2012 05:41
Favicon

[Technical Errata Reported] RFC6030 (3418)


The following errata report has been submitted for RFC6030,
"Portable Symmetric Key Container (PSKC)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6030&eid=3418

--------------------------------------
Type: Technical
Reported by: Simon Josefsson <simon@...>

Section: 7 and 11

Original Text
-------------
Section 7:
       <Signature>

Section 11:
               <xs:element name="Signature"
                    type="ds:SignatureType" minOccurs="0"/>

Corrected Text
--------------
Section 7:
       <ds:Signature>

Section 11:
               <xs:element ref="ds:Signature" minOccurs="0"/>
(Continue reading)

Sean Turner | 27 Nov 2012 01:09

Re: [Editorial Errata Reported] RFC6030 (3370)

Any objections to marking this as accepted?  Seems right to me.

spt

On 10/3/12 4:04 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6030,
> "Portable Symmetric Key Container (PSKC)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6030&eid=3370
>
> --------------------------------------
> Type: Editorial
> Reported by: Simon Josefsson <simon@...>
>
> Section: 6.3
>
> Original Text
> -------------
>         id="KC0001"
>
>
>
> Corrected Text
> --------------
>         Id="KC0001"
>
>
>
(Continue reading)

Simon Josefsson | 16 Oct 2012 10:07
Favicon
Gravatar

Bug in PSKC XML schema wrt XMLDsig?

All,

I have implemented support for XMLDsig protected PSKC and ran into an
issue with the XML Schema for PSKC.  It seems the Signature element is
in the wrong namespace, making it incompatible with the XMLDsig
specification.

There is a thread on this on the XMLSec mailing list:

http://thread.gmane.org/gmane.text.xml.xmlsec/4178

Both Aleksey Sanin (author of the XMLSec library) and G. Ken Holman (XML
expert) appear to believe this is an error in the schema:

http://thread.gmane.org/gmane.text.xml.xmlsec/4178/focus=4181
http://thread.gmane.org/gmane.text.xml.xmlsec/4178/focus=4185

The fix appears to be simple, but before filing an RFC errata for this
I'd thought I should bring this up in case anyone wants to comment.

Section 7:

OLD:
       <Signature>
NEW:
       <ds:Signature>

OLD:
       </Signature>
NEW:
(Continue reading)

Simon Josefsson | 11 Oct 2012 20:22
Favicon
Gravatar

Free software PSKC implementation

Hi all,

I wanted to let you know that I have just released a (partial) PSKC
implementation as free software in OATH Toolkit:

http://www.nongnu.org/oath-toolkit/

The tutorial is a good introduction to the functionality:

http://www.nongnu.org/oath-toolkit/libpskc-api/pskc-tutorial-pskctool.html
http://www.nongnu.org/oath-toolkit/libpskc-api/pskc-tutorial-quickstart.html

If anyone is interested in interop testing, please talk to me offlist.

/Simon
RFC Errata System | 3 Oct 2012 09:47
Favicon

[Technical Errata Reported] RFC6030 (3369)


The following errata report has been submitted for RFC6030,
"Portable Symmetric Key Container (PSKC)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6030&eid=3369

--------------------------------------
Type: Technical
Reported by: Simon Josefsson <simon@...>

Section: 4.3.1

Original Text
-------------
   <Manufacturer>:  This element indicates the manufacturer of the
      device.  Values for the <Manufacturer> element MUST be taken from
      either [OATHMAN] prefixes (i.e., the left column) or from the IANA
      Private Enterprise Number Registry [IANAPENREG], using the
      Organization value.  When the value is taken from [OATHMAN],
      "oath."  MUST be prepended to the value (e.g., "oath.<prefix value
      from [OATHMAN]>").  When the value is taken from [IANAPENREG],
      "iana."  MUST be prepended to the value (e.g., "iana.<Organization
      value from [IANAPENREG]>").

Corrected Text
--------------
   <Manufacturer>:  This element indicates the manufacturer of the
      device.  Values for the <Manufacturer> element MAY be taken from
(Continue reading)

RFC Errata System | 26 Sep 2012 00:55
Favicon

[Editorial Errata Reported] RFC6030 (3364)


The following errata report has been submitted for RFC6030,
"Portable Symmetric Key Container (PSKC)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6030&eid=3364

--------------------------------------
Type: Editorial
Reported by: Simon Josefsson <simon@...>

Section: 3

Original Text
-------------
      ----------------        ----------------
      | KeyPackage   |    0..1| DeviceInfo   |
      |--------------|--------|--------------|
      |              |--      | SerialNumber |
      ----------------  |     | Manufacturer |
              |         |     | ....         |
              |         |     ----------------

Corrected Text
--------------
      ----------------        ----------------
      | KeyPackage   |    0..1| DeviceInfo   |
      |--------------|--------|--------------|
      |              |--      | SerialNo     |
(Continue reading)

RFC Errata System | 17 Oct 2011 18:39
Favicon

[Editorial Errata Reported] RFC6063 (2999)


The following errata report has been submitted for RFC6063,
"Dynamic Symmetric Key Provisioning Protocol (DSKPP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6063&eid=2999

--------------------------------------
Type: Editorial
Reported by: Gareth Richards <gareth.richards@...>

Section: 4.2.4

Original Text
-------------
           DSKPP Client                         DSKPP Server
           ------------                         ------------
           E(K,R_C), AD          --->

Corrected Text
--------------
           DSKPP Client                         DSKPP Server
           ------------                         ------------
           E(K,R_C), [AD]          --->

Notes
-----
The AD is carried in the <KeyProvClientHello> if sent as a result of a trigger and so is optional in the <ekyProvClientNonce>.

(Continue reading)

Anders Rundgren | 8 Oct 2011 11:28
Picon

KEYPROV/DSKPP Successor

http://webpki.org/papers/keygen2/sks-keygen2-exec-level-presentation.pdf

Unlike the original KEYPROV effort this scheme is NOT a protocol,
it is a complete architecture.

This is how Apple would do it: create all the software AND hardware
needed for a pleasant "end user experience".

-- Anders


Gmane