Inspection and authentication of color security deterrents with multiple imaging devices

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Inspection and authentication of color security deterrents with multiple imaging devices
# 1  
Old 01-23-2010
Inspection and authentication of color security deterrents with multiple imaging devices

HPL-2010-8 Inspection and authentication of color security deterrents with multiple imaging devices - Aronoff, Jason S.; Simske, Steven J.
Keyword(s): Payload density, grayscale pre-compensation, authentication
Abstract: The use of 2D color barcodes is quickly becoming commonplace on printed packaging and labels. The color barcode allows for a higher data density in comparison to its 1D or 2D black and white counterparts. However, with the introduction of color, a new set of imaging problems is introduced in reading ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Cybersecurity

Two Factor Authentication – Best for the UNIX/Linux Server Security

The UNIX/Linux server security is challenging because these servers are at a risk of getting compromised at any point of time by the attackers. In today's enterprise environment, the UNIX and Linux servers are growing popular. With their increased popularity, these servers have become the primary... (1 Reply)
Discussion started by: reve-secure
1 Replies

2. Solaris

Veritas - multiple devices with same name

After removing a disk for replacement in Veritas (vdiskadm 4), the Sun engineer offlined the disk, and physically replaced it. After that there were two entries with the same device name. I have tried removing the disks with vxdisk rm and ran vxdctl enable, but nothing helps vxdisk list showed... (2 Replies)
Discussion started by: floydm
2 Replies
Login or Register to Ask a Question
sasl_getprop(10 July 2001)												sasl_getprop(10 July 2001)

NAME
sasl_getprop - Get a SASL property SYNOPSIS
#include <sasl/sasl.h> int sasl_getprop(sasl_conn_t *conn, int propnum, const void ** pvalue); DESCRIPTION
sasl_getprop gets the value of a SASL property. For example after successful authentication a server may wish to know the authorization name. Or a client application may wish to know the strength of the negotiated security layer. conn is the SASL connection object. propnum is the identifier for the property requested and pvalue is filled in on success. List of prop- erties follows: SASL_USERNAME - pointer to NUL terminated user name SASL_SSF - security layer security strength factor, if 0, call to sasl_encode, sasl_decode unnecessary SASL_MAXOUTBUF - security layer max output buf unsigned SASL_DEFUSERREALM - server authentication realm used SASL_GETOPTCTX - context for getopt callback SASL_IPLOCALPORT - local address string SASL_IPREMOTEPORT - remote address string SASL_SERVICE - service passed to sasl_*_new SASL_SERVERFQDN - serverFQDN passed to sasl_*_new SASL_AUTHSOURCE - name of auth source last used, useful for failed authentication tracking SASL_MECHNAME - active mechanism name, if any SASL_PLUGERR - similar to sasl_errdetail RETURN VALUE
Returns SASL_OK on success. SASL error code on failure. CONFORMING TO
RFC 2222 SEE ALSO
sasl(3), sasl_errors(3), sasl_server_new(3), sasl_client_new(3) SASL man pages SASL sasl_getprop(10 July 2001)